To have the same state on two branches you would need to run the same queries that you ran on the other branch.
To have the same state on two branches you would need to run the same queries that you ran on the other branch.
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.
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.