Hacker News Reader

Comment by deathclassic | Hacker News Reader

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.

View on HN

I take it you're not aware that the default database of new Django projects created by the admin commands is SQLite?

It's been at least 3 years since I did anything with django and that was with mysql.

Why? 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/

Ignore 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.

I'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.

Agreed 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.

Doesn't django use sqlite by default?

Yes 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/

Reply on news.ycombinator.com