3 ms·
SQLite is perhaps a little easier because you only have one file to think about, backups, etc. I use both but give preference to Postgres/PostGIS if I have to
by simplecto 7y ago
SQLite is perhaps a little easier because you only have one file to think about, backups, etc.
I use both but give preference to Postgres/PostGIS if I have to do mapping things.
MySQL is never a consideration for me.
- ddxxdd 7y agoIs there a particular reason why you never consider MySQL? I am honestly thinking of reworking my project (for the 10th time, lol) to convert a bunch of interconnected list-of-objects in Python into SQL databases. I'm talking about data on tens of thousands of political candidates, data on hundreds of thousands of political committees/SuperPACS, data on hundreds of federal elections, etc. I also just remembered that I have a MySQL server already installed on my computer. Given that I am working with several gigabytes of highly interconnected data, would it be worth installing PostGres on my machine?
- simplecto 7y agoI don't consider MySQL since I've invested so much time to learn PostgreSQL and its ecosystem of extensions. MySQL is a proved database, but my money is simply on a different horse.
- boznz 7y agomysql is fine. but there again I prefer coke over pepsi and ford over gm