> include primary key identifiers or timestamp values in your pagination strategy
And then we got that one customer that somehow backfilled old timestamped data and complained our pagination broke :(
And then we got that one customer that somehow backfilled old timestamped data and complained our pagination broke :(
I've also dealt with databases without column-level privileges. Where not handled by a column-level privilege system, it may still be possible to block this sort of UPDATE using a TRIGGER designed to fail.
Privilege grant (or drop of the trigger) could be used when the system is in an offline maintenance mode should you require the ability to correct that protected data, reinstituting the control when the maintenance is complete.
The criticality of the data and the level of automation in use would probably be the factors I would use to decide whether this overhead was warranted. Hopefully you had backups available.
It occurred when the clock on the hardware got messed up :(