Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

On Sun, Aug 14, 2016 at 04:02:19PM +0200, Chris Travers wrote: > One example is of such a service locator is > http://search.cpan.org/dist/PGObject-Simple/lib/PGObject/Simple.pm > > It runs as a library which helps the program decide how to do the call. > Currently it looks in the system catalog

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

On Sun, Aug 14, 2016 at 3:42 PM, Karsten Hilbert wrote: > Hello Chris, > > I am getting closer but ... > > > > > Sure. What I prefer to do is to allow for a (cacheable) lookup on > the > > > > basis of some criteria, either: > > > > 1. Function name or > > > > 2. Function name and first argume

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

Hello Chris, I am getting closer but ... > > > Sure. What I prefer to do is to allow for a (cacheable) lookup on the > > > basis of some criteria, either: > > > 1. Function name or > > > 2. Function name and first argument type > > > > > > This assumes that whichever discovery criteria you are

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

On Sun, Aug 14, 2016 at 12:35 PM, Karsten Hilbert wrote: > On Fri, Aug 12, 2016 at 01:32:33PM +0200, Chris Travers wrote: > > >>> My preference is stored procedures plus service locators > >> > >> Would you care to elaborate a little on the latter (service locators) ? > >> > > > > Sure. What I p

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

On Fri, Aug 12, 2016 at 01:32:33PM +0200, Chris Travers wrote: >>> My preference is stored procedures plus service locators >> >> Would you care to elaborate a little on the latter (service locators) ? >> > > Sure. What I prefer to do is to allow for a (cacheable) lookup on the > basis of some c

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

On Fri, Aug 12, 2016 at 11:32 AM, Karsten Hilbert wrote: > På fredag 12. august 2016 kl. 10:33:19, skrev Chris Travers < > chris.trav...@gmail.com[chris.trav...@gmail.com]>: > > > My preference is stored procedures plus service locators > > I know your work on the former with respect to the finan

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

On Fri, Aug 12, 2016 at 11:24 AM, Daevor The Devoted wrote: > > > On Fri, Aug 12, 2016 at 10:58 AM, Andreas Joseph Krogh > wrote: > > Could you elaborate on this method? Or direct me to docs describing it in > more detail? I'm quite interested in this approach, but would like to see > what amoun

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

På fredag 12. august 2016 kl. 10:33:19, skrev Chris Travers :   > My preference is stored procedures plus service locators I know your work on the former with respect to the financial app you are working on. Would you care to elaborate a little on the latter (service locators) ? Thanks, Karsten

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

På fredag 12. august 2016 kl. 11:24:16, skrev Daevor The Devoted < doll...@gmail.com >:   [snip] If you don't like your domain-model to be very close to your physical DB-model, there's nothing preventing you from having a persistence-model, using the ORM, and map that to

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

On Fri, Aug 12, 2016 at 10:58 AM, Andreas Joseph Krogh wrote: > På fredag 12. august 2016 kl. 10:33:19, skrev Chris Travers < > chris.trav...@gmail.com>: > > > > On Fri, Aug 12, 2016 at 9:59 AM, Andreas Joseph Krogh > wrote: >> >> På fredag 12. august 2016 kl. 05:27:42, skrev Chris Travers < >>

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

På fredag 12. august 2016 kl. 11:07:08, skrev Chris Travers < chris.trav...@gmail.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 wel

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

On Fri, Aug 12, 2016 at 10:58 AM, Andreas Joseph Krogh wrote: > På fredag 12. august 2016 kl. 10:33:19, skrev Chris Travers < > chris.trav...@gmail.com>: > > > > >> >> 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

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

På fredag 12. august 2016 kl. 10:33:19, skrev Chris Travers < chris.trav...@gmail.com >:     On Fri, Aug 12, 2016 at 9:59 AM, Andreas Joseph Krogh mailto:andr...@visena.com>> wrote: På fredag 12. august 2016 kl. 05:27:42, skrev Chris Travers mailto:chris.trav...@gma

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

On Fri, Aug 12, 2016 at 9:59 AM, Andreas Joseph Krogh wrote: > På fredag 12. august 2016 kl. 05:27:42, skrev Chris Travers < > chris.trav...@gmail.com>: > > > > On Thu, Aug 11, 2016 at 10:20 PM, Andreas Joseph Krogh > wrote: >> >> På torsdag 11. august 2016 kl. 19:13:08, skrev support-tiger < >>

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

På fredag 12. august 2016 kl. 05:27:42, skrev Chris Travers < chris.trav...@gmail.com >:     On Thu, Aug 11, 2016 at 10:20 PM, Andreas Joseph Krogh mailto:andr...@visena.com>> wrote: På torsdag 11. august 2016 kl. 19:13:08, skrev support-tiger mailto:supp...@tigerna

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

On Thu, Aug 11, 2016 at 10:20 PM, Andreas Joseph Krogh wrote: > På torsdag 11. august 2016 kl. 19:13:08, skrev support-tiger < > supp...@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 bein

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

On Thu, Aug 11, 2016 at 4:20 PM, Andreas Joseph Krogh wrote: > På torsdag 11. august 2016 kl. 19:13:08, skrev support-tiger < > supp...@tigernassau.com>: > > A database is only as good as the ability to use it. Using ORM's with > Postgres seems dumb, like having a Ferrari but only allowed to dri

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

På torsdag 11. august 2016 kl. 19:13:08, skrev support-tiger < supp...@tigernassau.com >: A database is only as good as the ability to use it.  Using ORM's with Postgres seems dumb, like having a Ferrari but only allowed to drive 25 kmh. Really, for getting data in

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

support-tiger wrote: > It would be great if the Ruby and Node drivers can be brought under the > Postgres team umbrella and make them as reliable and clearly documented as > the Python or jdbc drivers. Sadly, the PostgreSQL development group does not have the manpower to maintain or document clie

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

On 08/11/2016 10:43 AM, David G. Johnston wrote: On Thu, Aug 11, 2016 at 1:13 PM, support-tiger mailto:supp...@tigernassau.com>>wrote: It would be great if the Ruby and Node drivers can be brought under the Postgres team umbrella and make them as reliable and clearly documented as th

Re: [GENERAL] Postgres Pain Points 2 ruby / node language drivers

On Thu, Aug 11, 2016 at 1:13 PM, support-tiger wrote: > It would be great if the Ruby and Node drivers can be brought under the > Postgres team umbrella and make them as reliable and clearly documented as > the Python or jdbc drivers. What makes you say that the Python are JDBC drivers are "und

[GENERAL] Postgres Pain Points 2 ruby / node language drivers

A database is only as good as the ability to use it. Using ORM's with Postgres seems dumb, like having a Ferrari but only allowed to drive 25 kmh. Really, for getting data in and out with Postgres, SQL is pretty simple. The ORM abstractions take as much effort as simply writing direct SQL stat