Create, read, update and delete
In computer programming, create, read, update, and delete (CRUD) are the four basic functions of persistent storage. Alternate words are sometimes used when defining the four basic functions of CRUD, such as retrieve instead of read, modify instead of update, or destroy instead of delete. CRUD 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. 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 be easily held in memory.
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 Structured Query Language (SQL) statement, Hypertext Transfer Protocol (HTTP) method (this is typically used to build RESTful APIs) or Data Distribution Service (DDS) operation:
|Create||INSERT||PUT / POST||POST||write|
|Read (Retrieve)||SELECT||GET||GET||read / take|
|Update (Modify)||UPDATE||PUT / POST / PATCH||PUT||write|
The comparison of the database oriented CRUD operations to the HTTP methods has some flaws. Strictly speaking, both PUT and POST can create and update resources; the key difference is that contrary to POST, PUT is idempotent, meaning that multiple identical requests should have the same effect as a single request. Consequently PUT is a "replace" operation, which one could argue is not "update".
Although a relational database provides a common persistence layer in software applications, numerous other persistence layers exist. CRUD functionality can for example be implemented with object databases, XML databases, flat text files, or custom file formats. Some (big data) systems do not implement UPDATE, but have only a timestamped INSERT (journaling), actually storing a new version of the object. As a consequence they do not have transactions either, and might miss consistency.
This section has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)(Learn how and when to remove this template message)
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, or remove 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).
Other variations of CRUD include:
- BREAD (Browse, Read, Edit, Add, Delete) 
- DAVE (Delete, Add, View, Edit)
- CRAP (Create, Replicate, Append, Process)
- CRUDE (Create, Read, Update, Delete, Experience)
- Representational state transfer (REST)
- Active record pattern
- Data manipulation language
- Query by Example
- Command–query separation
- Managing the Data-base Environment, p. 381, at Google Books
- Heller, Martin (29 January 2007). "REST and CRUD: the Impedance Mismatch". Developer World. InfoWorld.
- Martin, James (1983). Managing the Data-base Environment. Englewood Cliffs, New Jersey: Prentice-Hall. p. 381. ISBN 0-135-50582-8.
- Tom Spencer (2014). "No REST for the whippet".
- Paul M. Jones (2008). "BREAD, not CRUD".
- McGaw, James. Beginning Django E-Commerce. p. 41.
- "CRAP and CRUD: From Database to Datacloud - Direct2DellEMC". Direct2DellEMC. 2012-11-13. Retrieved 2018-01-30.