Re: Postgres Pain Points 2 ruby / node language drivers

From: Andreas Joseph Krogh <andreas(at)visena(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Postgres Pain Points 2 ruby / node language drivers
Date: 2016-08-12 09:21:07
Message-ID: VisenaEmail.ca.1e1a8beafe4b846e.1567e0bc660@tc7-visena
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

På fredag 12. august 2016 kl. 11:07:08, skrev Chris Travers <
chris(dot)travers(at)gmail(dot)com <mailto:chris(dot)travers(at)gmail(dot)com>>:
[snip]
My preference is stored procedures plus service locators, to be honest.  It
enables a degree of loose coupling and even dynamic discovery that ORMs are
generally not well suited to.
 
But I think the difference may be bigger.  ORMs make sense when you want a
database for your application.  They break down badly when you want an
application for your database.  Usually I tend to want the latter.
 

 
I'm in the first group, and I think many are when evaluating ORMs or having an
opinion about them. Being in the latter, I more understand you concerns.
 
-- Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>

 

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Daevor The Devoted 2016-08-12 09:24:16 Re: Postgres Pain Points 2 ruby / node language drivers
Previous Message Andrus 2016-08-12 09:18:44 Re: How to parse xml containing optional elements