79
Consider SQLite (blog.wesleyac.com)
submitted 3 years ago by to c/programming@programming.dev
66 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[+] 9 points 3 years ago* (last edited 3 years ago) (4 children)
[deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 3 years ago (2 children)

    Proper = has actual admin tooling vs. just a file format.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [+] 3 points 3 years ago* (last edited 3 years ago) (1 child)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 3 years ago

    The database in a state where it's violating some assumptions I'm making and I need to manually intervene without taking down my application for example. I need to have an audit trail on the changes being made to the database and who made them. I need to create replicas to implement failover. I need to replicate my application on multiple machines and all the replicas need to have the same view of the data. I need to mitigate the possibility of data leaks if I have multiple tenants sharing a database.

    I'm not saying that you're wrong for using it. I'm just saying that it doesn't work for everything.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 3 years ago

    I typically run postgres locally too (in docker), while there's still technically network overhead there's not much compared to a real network, plus you can easily move it to another machine without reworking your app to switch from SQLite to postgres.

  • permalink
  • fedilink
  • source
  • parent