That doesn't let you merge in someone else's changes easily. Aka two team members make changes to the (local copy of) database and now you want to merge it.
I mean sure you can have another database tracking their changes and a merging algorithm but that's what dolt is doing for you
That is, you can:
1. Create a table with an extra changeset id column and a branch id column, so that you can keep historical values.
2. Have a view on that table with the latest version of each record on the master branch.
3. Express branching-related actions as actions on the main table with different record versions and branch names
4. For the chocolate sprinkles, have tables with changeset info and branch info
and that gives you a poor man's git already - doesn't it?