3 ms·
This really isn't that weird. Imagine you had auditing requirements for a SQL database that you must know when the last time each row was accessed. But in this
by Spivak 6y ago
This really isn't that weird. Imagine you had auditing requirements for a SQL database that you must know when the last time each row was accessed. But in this universe the SQL database is your only persistent datastore (because machines might only have one partition and your system must still function when there is only one partition) so you have to store access times in the rows.
But your SQL server only has two modes, the whole database is read-only or the whole database is read-write. You really wish there was a soft read-only where only the auditing data is allowed to be updated but it doesn't exit. So now you're stuck with read-only replicas of your database being noncomplaint.
It's a problem that really has no good solution outside of the filesystem driver supporting this mode.