(1) SQLite did never claim to be as "complete" as other databases -- it is and will be a "lightweight" database.
(2) Everybody with marginal knowledge of different databases should know, that using different databases always puts you on risk and needs extra testing. You would also not recommend to develop your application on Linux, use a crosscompiler and ship the product on Windows untested. And with that said, most of the arguments can be deleted.
(3) When you are using an ORM, most of the arguments are obsolete, too.
I don't know what you're talking about; is there even a downvote button on Hacker News? I certainly don't see one.
Some features that ORMs make unnecessarily difficult (or impossible without simply avoiding the use of the ORM) to use, off the top of my head:
* transactional DDL
* temporary tables
* user-defined data types
* asynchronous notifications
* dynamic SQL
* non-serial keys
* multi-attribute keys
* temporal schema
* window functions (really all manner of analytics queries)
Those were just the ones off of the top of my head, ones that are not "independent of SQL features."
Enjoy your flat-files, because that's actually what ORM gets you close to: a procedural abstraction inversion over a rich and capable declarative interface and first-order-logic engine.
You wrote, "when you are using an ORM, most of the arguments [against using a different DBMS for testing than production] are obsolete, too," which is false, unless the point of the ORM is to bring the production DBMS down to the test DBMS's level of capability.
Comments
Some comments on the arguments:
(1) SQLite did never claim to be as "complete" as other databases -- it is and will be a "lightweight" database.
(2) Everybody with marginal knowledge of different databases should know, that using different databases always puts you on risk and needs extra testing. You would also not recommend to develop your application on Linux, use a crosscompiler and ship the product on Windows untested. And with that said, most of the arguments can be deleted.
(3) When you are using an ORM, most of the arguments are obsolete, too.
At the cost of pretty much everything you get out of using something that isn't SQLite.
[deleted]
I don't know what you're talking about; is there even a downvote button on Hacker News? I certainly don't see one.
Some features that ORMs make unnecessarily difficult (or impossible without simply avoiding the use of the ORM) to use, off the top of my head:
* transactional DDL
* temporary tables
* user-defined data types
* asynchronous notifications
* dynamic SQL
* non-serial keys
* multi-attribute keys
* temporal schema
* window functions (really all manner of analytics queries)
Those were just the ones off of the top of my head, ones that are not "independent of SQL features."
Enjoy your flat-files, because that's actually what ORM gets you close to: a procedural abstraction inversion over a rich and capable declarative interface and first-order-logic engine.
To answer the downvote tidbit, there is and it shows up when your Karma is high enough. That threshold is not disclosed however.
[deleted]
You wrote, "when you are using an ORM, most of the arguments [against using a different DBMS for testing than production] are obsolete, too," which is false, unless the point of the ORM is to bring the production DBMS down to the test DBMS's level of capability.