Skip to content

Comment on Don't test with SQLite when you use Postgres in Productionparent

Comments

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]

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

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.