5 ms·
It would probably be harder to bend Django to use SQLite as a backend then it would be to just setup MySQL or PostGRES and use the existing Django tooling for i
by deathclassic 4y ago
It would probably be harder to bend Django to use SQLite as a backend then it would be to just setup MySQL or PostGRES and use the existing Django tooling for it.
- acdha 4y agoWhy? It’s been supported since the 2000s and is popular for test suites so it gets more exercise than you might think. https://docs.djangoproject.com/en/4.1/ref/databases/ https://docs.djangoproject.com/en/4.1/ref/databases/
- plonq 4y agoDoesn't django use sqlite by default?
- imran-iq 4y agoYes it does[0]. Which makes the parent comment even more hilarious. > By default, the configuration uses SQLite. --- 0: https://docs.djangoproject.com/en/4.1/intro/tutorial02/ https://docs.djangoproject.com/en/4.1/intro/tutorial02/
- bravura 4y agoAgreed perhaps, but I still don't want to devops Postgres and I'd rather having tiny hosting costs for tiny apps. So I think there's a definite need here for this tooling.
- irskep 4y agoI'm not convinced this is true. Django supports SQLite out of the box, and otherwise database management is an exercise for the reader. The migration tools, for example, work fine with SQLite.
- adamckay 4y agoI take it you're not aware that the default database of new Django projects created by the admin commands is SQLite?
- deathclassic 4y agoIt's been at least 3 years since I did anything with django and that was with mysql.
- deathclassic 4y agoIgnore this, I was wrong. Django supports sqlite just fine. Last time I did anything with django I was an intern and just copied the setup from the readme which happened to include a mysql setup. I have not touched django since.