4 ms·

Thanks for the details. I would be afraid to use SQLite over Postgres as SQLite is much more... flexible with it's database constraints (or at least, this used

Thanks for the details. I would be afraid to use SQLite over Postgres as SQLite is much more... flexible with it's database constraints (or at least, this used to be the case). Not knocking your engineering choices - if you've been running it in prod for years, then it's working for you - just interested. Do you lean into DB constraints much or do you do more application level checking/enforcement?

scns 5y ago
Not parent but mentioning nuget suggest parent is on dotnet, ie C/F# ergo semi-/typesafe. Parsing (not validating) at the edges should take care of it.
- bob1029 5y ago
  > Parsing (not validating) at the edges should take care of it. Precisely. We use a tiny ORM on top of Dapper to make sure everything goes in and out of columns as expected.
  - mekster 5y ago
    How is isolation important to use SQLite? Edge does not provide safety to every database modifications like manually editing data and you're screwed already.
    - bob1029 5y ago
      We never allow for manual edits of live SQLite databases. Everything happens through code. If someone wants to play around with a SQLite database from production, we just copy the file and hand it to them. That's kinda the whole point IMO.