The table customizer finds the stored row of an update by its id, and compared the two ids as they came: the id of a request over HTTP is text (it is the id in the path), the stored id is a number. They were never equal, so an edit made through the API or the UI had no stored row and was validated and stamped as an insert. The uniqueness check of a classification compared ids the same way. Both now compare the ids as text. This is older than the standard dates, but they build on it: the customizer gives a new row its create date, and a client that knows record versions edits a table with a modify date by sending only the changed values and the version it read. What an edit over HTTP did before: - A classification, policy or retention rule got a new create_date. - Releasing a legal hold overwrote when and by whom it was placed (and, since the hold has one, its create date). - Editing the reason of a legal hold without sending its status failed with a server error (the validation read the status of a row it did not have). - Editing a classification while naming its table and field was refused as a second classification of that field. - Editing a retention rule without sending every field was refused. Tests (SecuredDataHttpEditTest, through the real middleware on the shipped schema, a day after the rows were written): the reason of a hold is edited with the changed value and the version, and the stale version is then refused; a hold is released and keeps when and by whom it was placed and its create date; a classification is edited naming its table and field; a policy and a retention rule are renamed and keep their create dates; a row with neither date is read and edited. All five fail without the fix. They run in UTC: where the default zone of the JVM is not UTC, core refuses every update that sends a version, which is core's to fix and is kept out of these tests. Notes for an upgrade (shipped DDL block and README): set a lock_timeout before the ALTER statements and run the block again when one is cancelled; on a large access log run its backfill UPDATE in ranges of id, or leave it out, since rows without the two dates are read and written like any others. Changelog: the fix, that an update naming the create date still sets it, and that a wipe moves the record version of its retention rule. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>