4 ms·

Supabase offers version controlled database? To be clear, what dolt does is enabling you to branch like git and then merge your branch, rollback old "commits" o

Supabase offers version controlled database? To be clear, what dolt does is enabling you to branch like git and then merge your branch, rollback old "commits" of your database and similar stuff. It is much more advanced than audit logging

boomskats 3y ago
How does DoltgreSQL compare to Neon's branching?
- willi59549879 3y ago
  In neon you can create different branches but there is no merge functionality. I think merge functionality is very hard to implement anyway. not sure if it is worth the effort. To have the same state on two branches you would need to run the same queries that you ran on the other branch.
  - andrenotgiant 3y ago
    > not sure if it is worth the effort. Exactly. Teams that are mature enough to use data branching in development likely already have a schema migration tool that handles the merge safely with all the necessary controls.
    - elaencam 3y ago
      And how about those teams that are starting out and don't want to build all of that? It's worth the effort given that it's a common problem that teams need to solve over and over.
      - zachmu 3y ago
        One of the biggest challenges for us has been getting through people's heads that "version controlled database" doesn't mean "schema migrations with extra steps". Some people get it immediately, but in general there's a real failure of imagination about what kind of use cases this technology enables. Our customers are building workflows that are just impossible to achieve with other databases. There are a few common use cases that come up over and over: * Game development, to version control game configuration data being edited by an entire team of developers at once * CMS-like tools, including online storefronts, so you can have pull request workflows and easy rollback * Collaborative data sourcing, where multiple independent sources get merged together into a single database There's also the distributed use case, where people fork and clone each other's data sets, that we haven't really seen take off yet. Or maybe those people are just unlikely to buy hosting services or file support tickets.
- zachmu 3y ago
  Neon is basically a copy on write postgres backend. So you can create a branch at near zero cost and start making changes, but there's no way to merge those changes back to the original branch. To do that, you need a storage system that can efficiently compute a diff to do a three-way merge. That's what dolt does. It means you can diff any two commits in the database with cost proportional to the size of the diff, not the size of the data. And it uses a commit graph just like git which enables it to find common ancestors for a three-way merge algorithm, again just like git.

boomskats 3y ago

How does DoltgreSQL compare to Neon's branching?

willi59549879 3y ago
In neon you can create different branches but there is no merge functionality. I think merge functionality is very hard to implement anyway. not sure if it is worth the effort. To have the same state on two branches you would need to run the same queries that you ran on the other branch.
- andrenotgiant 3y ago
  > not sure if it is worth the effort. Exactly. Teams that are mature enough to use data branching in development likely already have a schema migration tool that handles the merge safely with all the necessary controls.
  - elaencam 3y ago
    And how about those teams that are starting out and don't want to build all of that? It's worth the effort given that it's a common problem that teams need to solve over and over.
    - zachmu 3y ago
      One of the biggest challenges for us has been getting through people's heads that "version controlled database" doesn't mean "schema migrations with extra steps". Some people get it immediately, but in general there's a real failure of imagination about what kind of use cases this technology enables. Our customers are building workflows that are just impossible to achieve with other databases. There are a few common use cases that come up over and over: * Game development, to version control game configuration data being edited by an entire team of developers at once * CMS-like tools, including online storefronts, so you can have pull request workflows and easy rollback * Collaborative data sourcing, where multiple independent sources get merged together into a single database There's also the distributed use case, where people fork and clone each other's data sets, that we haven't really seen take off yet. Or maybe those people are just unlikely to buy hosting services or file support tickets.
zachmu 3y ago
Neon is basically a copy on write postgres backend. So you can create a branch at near zero cost and start making changes, but there's no way to merge those changes back to the original branch. To do that, you need a storage system that can efficiently compute a diff to do a three-way merge. That's what dolt does. It means you can diff any two commits in the database with cost proportional to the size of the diff, not the size of the data. And it uses a commit graph just like git which enables it to find common ancestors for a three-way merge algorithm, again just like git.