>>It's illogical the before and after (dump reloaded) state of the table to not be the same. >That's false. A dump isn't in any way under contract to preserve the "state" of the DB, only the Schema and persistent Data. OK, let's play your way. Should persistent data be restored? According to your quoted sentence above it should. In the my table I have one STORED column along with normal columns. Due to this problem, a table that had hundreds of rows now only has two. The rows with the persistent data were not loaded due to the collision of keys which didn't happen in the original but now all times are the same and rejected as duplicates. You have to be able to at least load the rest of the row columns even if the STORED (which proves to be a misnomer) column contains garbage.