Re: [HACKERS] Feasibility of supporting bind params for all command types

2014-10-07 Thread Craig Ringer
On 10/06/2014 10:13 AM, Tom Lane wrote: I think it might be desirable but it'd be a mess, both as to the concept/definition and as to the implementation. Thanks Tom. The issues around ALTER etc pretty much put it in the not-worth-caring-about bucket. The issues around parameter typing alone...

Re: [HACKERS] Feasibility of supporting bind params for all command types

2014-10-06 Thread Greg Sabino Mullane
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Tom Lane said: ... Craig Ringer cr...@2ndquadrant.com writes: While looking at an unrelated issue in PgJDBC I noticed that it's difficult for users and the driver to tell in advance if a given statement will support bind parameters. It's

[HACKERS] Feasibility of supporting bind params for all command types

2014-10-05 Thread Craig Ringer
Hi all While looking at an unrelated issue in PgJDBC I noticed that it's difficult for users and the driver to tell in advance if a given statement will support bind parameters. PostgreSQL just treats placeholders as syntax errors for non-plannable statements at parse time. This forces users to

Re: [HACKERS] Feasibility of supporting bind params for all command types

2014-10-05 Thread Tom Lane
Craig Ringer cr...@2ndquadrant.com writes: While looking at an unrelated issue in PgJDBC I noticed that it's difficult for users and the driver to tell in advance if a given statement will support bind parameters. It's not that hard ;-) ... if it ain't SELECT/INSERT/UPDATE/DELETE, it won't