Jump to content

Create, read, update and delete: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Line 44: Line 44:


== User interface ==
== User interface ==
CRUD is also relevant at the user interface level of most applications. For example, in [[address book]] software, the basic storage unit is an individual ''[[contact (social)|contact]] entry''. As a bare minimum, the software must allow the user to:
CRUD is also relevant at the user interface level of most applications. For example, in [[address book]] software, the basic storage unit is an individual ''[[contact (social)|contact]] entry''. As a bare minimum, the software must allow the user to


'''* Create or add new entries
''* Create or add new entries
* Read, retrieve, search, or view existing entries
* Read, retrieve, search, or view existing entries
* Update or edit existing entries
* Update or edit existing entries
* Delete/deactivate existing entries'''''''''Bold text''''''
* Delete/deactivate existing entries'''


Without at least these four operations, the software cannot be considered complete. Because these operations are so fundamental, they are often documented and described under one comprehensive heading, such as "contact management", "content management" or "contact maintenance" (or "document management" in general, depending on the basic storage unit for the particular application).
Without at least these four operations, the software cannot be considered complete. Because these operations are so fundamental, they are often documented and described under one comprehensive heading, such as "contact management", "content management" or "contact maintenance" (or "document management" in general, depending on the basic storage unit for the particular application).

Revision as of 09:35, 18 March 2014

In computer programming, create, read, update and delete (CRUD) (Sometimes called SCRUD with an "S" for Search) are the four basic functions of persistent storage.[1] Sometimes CRUD is expanded with the words retrieve instead of read, modify instead of update, or destroy instead of delete. It is also sometimes used to describe user interface conventions that facilitate viewing, searching, and changing information; often using computer-based forms and reports. The term was likely first popularized by James Martin in his 1983 book Managing the Data-base Environment.[2][3] The acronym may be extended to CRUDL to cover listing of large data sets which bring additional complexity such as pagination when the data sets are too large to hold easily in memory.

Another variation of CRUD is BREAD, an acronym for "Browse, Read, Edit, Add, Delete".

Database applications

The acronym CRUD refers to all of the major functions that are implemented in relational database applications. Each letter in the acronym can map to a standard SQL statement and HTTP method:

Operation SQL HTTP
Create INSERT PUT / POST
Read (Retrieve) SELECT GET
Update (Modify) UPDATE PUT / PATCH
Delete (Destroy) DELETE DELETE

Although a relational database provides a common persistence layer in software applications, numerous other persistence layers exist. CRUD functionality can be implemented with an object database, an XML database, flat text files, custom file formats, tape, or card, for example.

User interface

CRUD is also relevant at the user interface level of most applications. For example, in address book software, the basic storage unit is an individual contact entry. As a bare minimum, the software must allow the user to

* Create or add new entries

  • Read, retrieve, search, or view existing entries
  • Update or edit existing entries
  • Delete/deactivate existing entries

Without at least these four operations, the software cannot be considered complete. Because these operations are so fundamental, they are often documented and described under one comprehensive heading, such as "contact management", "content management" or "contact maintenance" (or "document management" in general, depending on the basic storage unit for the particular application).

See also

Notes

  1. ^ Heller, Martin (29 January 2007). "REST and CRUD: the Impedance Mismatch". Developer World. InfoWorld.
  2. ^ Managing the Data-base Environment, p. 381, at Google Books
  3. ^ Martin, James (1983). Managing the Data-base Environment. Englewood Cliffs, New Jersey: Prentice-Hall. p. 381. ISBN 0-135-50582-8.