Create, read, update and delete (CRUD) are the four basic functions of persistent storage.[1] Sometimes CRUD is expanded with the words retrieve instead of read 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.
Contents |
Terminology
Google Scholar lists the first reference to create-read-update-delete as by Haim Kilov in 1990.[2][3] The concept is described in more detail in Kilov's 1998 book.[4]
Alternative abbreviations to CRUD:
- ABCD: add, browse, change, delete
- ACID: add, change, inquire, delete — though this can be confused with the transactional use of the acronym ACID.
- BREAD: browse, read, edit, add, delete
- VADE(R): view, add, delete, edit (and restore, for systems supporting transaction processing)
- QDIM: query, delete, insert, modify
- SAID: show, alter, insert, delete
- VEDAS: view, edit, delete, add, search
- SCUD: select, create, update, delete
Database applications
The acronym CRUD refers to all of the major functions that need to be implemented in a relational database application to consider it complete. Each letter in the acronym can be mapped to a standard SQL statement:
| Operation | SQL |
|---|---|
| Create | INSERT |
| Read (Retrieve) | SELECT |
| Update | UPDATE |
| Delete (Destroy) | DELETE |
Although a relational database is a common persistence layer in software applications, there are numerous others. CRUD 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 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" or "contact maintenance" (or "document management" in general, depending on the basic storage unit for the particular application).
See also
- Representational State Transfer RESTful
Notes
- ^ Strategic Developer | Martin Heller | InfoWorld | REST and CRUD: the Impedance Mismatch | January 29, 2007 06:00 AM | By Martin Heller
- ^ [1] Kilov, Haim (1990) From semantic to object-oriented data modeling. First International Conference on System Integration, 1990. 385 - 393.
- ^ http://ieeexplore.ieee.org/Xplore/login.jsp?url=/iel2/482/3754/00138704.pdf?arnumber=138704
- ^ Amazon.com: Business Specifications: The Key to Successful Software Engineering: Haim Kilov: Books
 |
This article includes a list of references or external links, but its sources remain unclear because it has insufficient inline citations. Please help to improve this article by introducing more precise citations where appropriate. (November 2008) |
|
||||||||||||||||||||
 |
This database-related article is a stub. You can help Wikipedia by expanding it. |
This entry is from Wikipedia, the leading user-contributed encyclopedia. It may not have been reviewed by professional editors (see full disclaimer)
