3 ms·

Is it for versions of the database design or versions of the data?

• deleted 6y ago
  [deleted]
• skybrian 6y ago
  Both. Schema changes are versioned like everything else. But depending on what the change is, it might make merges difficult. (I haven’t used it; I just read the blog.)
  • fiedzia 6y ago
    BTW. I wish all databases versioned their schema and kept full history. This should be a standard feature.
    • codesnik 6y ago
      keep history just as a changelog to see when and what was changed? or something with versions you actively can revert to? I suppose one of the problems is that changing schema is usually interleaved with some sorts of data migrations and conversion and those I have no idea how to track without using some general scripting language, like migrations in many frameworks which are already there.
      • fiedzia 6y ago
        Just storing a changelog would be very useful. I could for example compare db version some app was developed for with current state. Most companies will store schema migrations in git, but doing anything with this information is difficult. Having this in db would make automated checks easier.