Contributed by: remy Thursday, 29 August 2013, 10:28 @ CEST
In reference to http://en.wikipedia.org/wiki/CRUD[*1]
The CRUD pattern is most basic to information systems. It is a obvious thought that any file should be equipped with a CRUD based maintenance program. That is a program, or a collection of programs that can Add a record to a file (Create), Read that record back (Retrieve), Update some fields (Update) and Delete a record permanently (Delete).
The pattern is quite suited for an automated approach. Besides the field names of the file are different for any file, there is no change in the logic of the program.
And it is easy to manage your own templates for CRUD programs. If you do so you might consider to extend CRUD with "List" that contains functions like navigation and pagination.
In several systems, CRUD also refers to some security measures. CRUD becomes a role or a rights system. When this is the case, it is strongly advised to extend CRUD with "Exchange" (or "Export" or "Execute") that will handle the conversion of format like csv or xml.
Another variation of CRUD is BREAD, an acronym for "Browse, Read, Edit, Add, Delete".