Fwd: Support for OUT parameters in procedures
Dave Cramer <davecramer@postgres.rocks>
From: Dave Cramer <davecramer@postgres.rocks>
To: pgsql-jdbc@lists.postgresql.org
Date: 2020-10-05T10:54:23Z
Lists: pgsql-hackers
Just saw this on hackers. Anyon care to comment ? Dave Cramer www.postgres.rocks ---------- Forwarded message --------- From: Robert Haas <robertmhaas@gmail.com> Date: Fri, 28 Aug 2020 at 09:31 Subject: Re: Support for OUT parameters in procedures To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com> Cc: pgsql-hackers <pgsql-hackers@postgresql.org> On Fri, Aug 28, 2020 at 2:04 AM Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote: > The handling of results of SQL statements executed at the top level > (a.k.a. direct SQL) is implementation-specific and varies widely in > practice. More interesting in practice, in terms of functionality and > also compatibility, are nested calls in PL/pgSQL as well as integration > in JDBC. I agree that driver integration, and in particular JDBC integration, is important and needs some thought. I don't think it horribly matters, with a feature like this, what shows up when people type stuff into psql. Whatever it is, people will get used to it. But when they interact through a driver, it's different. It is no good inventing things, either in PostgreSQL or in the JDBC driver for PostgreSQL, that make PostgreSQL behave differently from every other database they use. I don't know exactly how we get to a good outcome here, but I think it's worth some careful consideration. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Support for OUT parameters in procedures
- 2453ea142233 14.0 landed