> We should manage the revision of data the way we manage the revision of our source code. I think some new features of e.g. Postgres allow for something like

> We should manage the revision of data the way we manage the revision of our source code. I think some new features of e.g. Postgres allow for something like this, but all SQL databases have the same basic design flaw: no inherent version control. SQL Databases are so big and complex that they haven't evolved much in 30 years. That's why there's so many "new" databases that are either a wrapper around Postgres, or trying to re-create parts of a relational database from scratch. It would be great if the next iteration of the SQL standard included version control semantics.