3 ms·
This seems to have minimal upside and heaps of downside - you can only use the features that every database has. You should be running the same database in tes
by djrobstep 6y ago
This seems to have minimal upside and heaps of downside - you can only use the features that every database has.
You should be running the same database in test as in production anyway - there are heaps of problems you won't catch if you don't.
- JonAtkinson 6y agoThe majority of apps need a very small subset of database features; they need somewhere to park strings and numbers in a reliable way, and retrieve them (sometimes in order). The Django ORM supports this across all of the backends it supports.
- djrobstep 6y agoStrong disagree - even the basic features and data types of databases have subtle but critical differences. You should be free to use the features available, not waste your time optimising for databases that don't have those features but that you will likely never switch to anyway.
- bb88 6y ago95-99% of your app is data and query optimization. And django seems to do all of this just fine really.