4 ms·
I don't think its intended to be used for frequently changed models like 'user'. It is much more suited for low change frequency document like models. For examp
by Vitaly 16y ago
I don't think its intended to be used for frequently changed models like 'user'. It is much more suited for low change frequency document like models. For example 'content' model in a blog or cms.
having history might not be a big deal, but having branches IS!.
It is great for stuff like testing some new set of pages on a staging server and then 'adding' them to the currently running production server which kept changing while you were working on the stage. Try that with SQL!
- pauldowman 16y agoYes, it would be a lot more appropriate for things that don't change that frequently. I actually started writing a blogging app for coders, and then succumbed to a bout of extraction distraction by generalizing the part that read the pages/posts from a Git repo: https://github.com/pauldowman/balisong https://github.com/pauldowman/balisong