Re: Postgres Pain Points 2 ruby / node language drivers - Mailing list pgsql-general

 

 

On Thu, Aug 11, 2016 at 10:20 PM, Andreas Joseph Krogh <andreas@visena.com> wrote:

På torsdag 11. august 2016 kl. 19:13:08, skrev support-tiger <support@tigernassau.com>:

 

I cannot not comment on this. Saying that ORM seems dumb, and working with PG using ORM does not fly, is a very good recipe for not being taken seriously.

 

And yet everyone I have talked to understands that ORMs are pretty problematic as a concept.  They make some things easy but they have some pretty massive downsides.  ORMs, it is true, do solve some problems, but they usually create many more in the process.  The reason is that as much as relations look like collections of objects, they are best organized along very different principles.  While we break down our tables based on functional dependencies between data values, we break down our object models based on how we can encapsulate state changes behind consistent interfaces.  The latter is dependent on use, while the former far less so.
 

Of course you *can* use them well.  I remember talking about this with one author or a major ORM and he said that on thing he often does is create views with triggers and then use the ORM against those.  This solves the problem above very well.  But it still leaves the fact that the database and the application have to share an implicit understanding of an object model and keeping that in sync as the project grows can be troublesome.