Timeline for Is it a bad practice to have a "record status" column in a database table?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 16, 2019 at 13:13 | comment | added | Frank Hopkins | Good answer, but there are alternative options, e.g. move the rows into a backup table from where you can recover them. The backup table can have minimal indices. This minimizes the issues you note with the existing approach (larger index, potential confusion for users of the table etc), but obviously adds the fact that you have another table to maintain (and means the entries are gone wrt to foreign key references). There are quite a few other options - but indeed those that come to mind are all some custom implementation, not something general provided by every SQL database for such cases. | |
| Feb 11, 2018 at 17:30 | vote | accept | ADTC | ||
| Mar 9, 2016 at 12:23 | history | answered | Phill W. | CC BY-SA 3.0 |