Hot answers tagged


Delete is delete. If you are hiding the data behind a flag, or removing it from your DB, or writing an archive to another table, or generating a transaction-log style audit entry, or wiping the bits off the disk a thousand times using randomly encrypted values... it doesn't matter. You've still deleted the data from the user's view. As far as a business ...


You call it "CRUD." Designating an app as a CRUD app is meant to indicate that a lot of its core functions center around common record-management tasks--the eponymous create, read, update, and delete. "CRUD" is not, however, meant to completely describe the app. CRUD apps have a range of activities, variations, and implementations. Some soft-delete, some ...


According to the Java Language Specification s. 8.1.3, "An inner class is a nested class that is not explicitly or implicitly declared static" As this is the most authoritative document on the Java language, the answer to your question is no, it is not incorrect to use this term.


The general term for having off-line "child" databases is replication. I don't believe there is standard term for those child databases only containing a defined part of the central database. Call it partial replication, if you like.


One interface I saw had options to Retire (soft-delete) or Delete (actually remove) data from the database.

Only top voted, non community-wiki answers of a minimum length are eligible