4 ms·
I'm (re) building a management interface for our product which offers a GUI to generate a configuration file with a lot of knobs and whatnot, and we're continui
by Cthulhu_ 6y ago
I'm (re) building a management interface for our product which offers a GUI to generate a configuration file with a lot of knobs and whatnot, and we're continuing to use SQLite.
There's three major things I'm still struggling with though:
- Should I switch from using an ORM (gorm) to using more raw SQL with some utilities to reduce tedium and boilerplate?
- Versioning; users will want to be able to revert to a previous version of a configuration (not just a single table, a set of tables)
- Redundancy; if the primary node fails, it should switch over to a secondary node, ideally in another location. The existing app copies the .db file to a `sync` folder after certain operations, which is then sent to the secondary server via rsync. It's actually pretty elegant if you think about it?
Anyway, none of these are really SQLite specific issues.
- akpa1 6y agoI use SQLite with GORM pretty regularly, and it works pretty nicely unless you're working with composite primary keys[0]. I've ended up writing some raw SQL to work around that, it's kinda annoying. [0]: https://github.com/go-gorm/gorm/issues/3585 https://github.com/go-gorm/gorm/issues/3585