3 ms·
One point made me wondering. From the article: > "for the same reasons developing on SQLite causes problems" I've used SQLite with Django and Flask where it w
by drdaeman 13y ago
One point made me wondering. From the article:
> "for the same reasons developing on SQLite causes problems"
I've used SQLite with Django and Flask where it was appropriate option (i.e. as a low-traffic low-volume simple database) and never had any problems. While there are things about SQLite one certainly has to be aware of (mostly related to the type system), I doubt SQLite causes more problems than any other RDBMS, as every one has its own specifics and quirks.
Am I unaware of something?
EDIT: Thanks, now I get it. Misunderstood what this quote was about.
- simonw 13y agoThat quote is about developing and testing on SQLite but deploying on another database such as PostgreSQL and MySQL. Unsurprisingly, doing so is likely to result in bugs that only occur in production.
- rom16384 13y agoThe point is not about avoiding SQLite when it makes sense to use it, but to have the same DB in the development and production environment. SQLite is much more permissive than, say, Postgres, and these differences mean that bugs could go unnoticed until deployment.
- deleted 13y ago[deleted]