3 ms·
I don't know what kind of magic fairy dust Django is but I've found the differences between SQLite and PostgreSQL too big to be worth it, in at least 3 other pr
by pdimitar 2y ago
I don't know what kind of magic fairy dust Django is but I've found the differences between SQLite and PostgreSQL too big to be worth it, in at least 3 other programming languages that are not Python.
Sounded good at first but we were quickly overwhelmed with false positives and just opted for Postgres in a VM (this was before Docker was a thing).
- herpdyderp 2y agoI've discovered the same thing: can't use SQLite to mock PostgreSQL. PGLite looks super promising for this, but I haven't tried it yet at scale.
- phendrenad2 2y agoThis is a good thing to be aware of when choosing a database, but I think most of the time people just reach for Postgres because it's the "standard".
- pdimitar 2y agoPostgreSQL stops many data bugs at the door due to being so strict -- something many programmers start rediscovering is a good thing by choosing stricter programming languages with time. I love SQLite to bits but the test harness I have to put around my apps with it is a separate project in itself.
- phendrenad2 2y agoSomehow this is my first time hearing about that benefit of Postgres! (despite having googled for explanations of why people were switching to it). Being on HN proves more valuable than google once again...
- pdimitar 2y agoGlad to help! On a philosophical / meta level it's all quite simple: do your damnedest for the computer to do as much of your work for you as possible, really. Nothing much to it. Strict technologies slap you hard when you inevitably make a mistake so they do in fact do more of your work for you.
- btilly 2y agoDjango is a Python-based ORM that works really well and has a large community. See https://www.djangoproject.com/ https://www.djangoproject.com/. If I have to do anything CRUD like, I'll use Django. For reporting apps, I prefer native SQL.