| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Greg Nancarrow <gregn4422(at)gmail(dot)com>, David Rader <david(dot)rader(at)gmail(dot)com>, pgsql-jdbc(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Procedure support improvements |
| Date: | 2019-08-26 17:48:23 |
| Message-ID: | CADK3HH+Bfat=byMsatf9VZ2VcG7Geu7=QJBSbJ8cTeE=sqtkAw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
On Mon, 26 Aug 2019 at 13:43, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> Dave Cramer wrote:
> > As I said, I'd entertain a connection parameter that switched the
> > CALL to call procedures but ideally you'd complain to the server
> > folks to make Procedures useful.
>
> Apart from the obvious problem that procedures make life hard for the
> JDBC driver, because it does not know if it shall render a call as
> SELECT or CALL:
> What is missing in PostgreSQL procedures to make them useful?
>
being able to use transactions inside a procedure inside a transaction.
Dave Cramer
davec(at)postgresintl(dot)com
www.postgresintl.com
>
> Yours,
> Laurenz Albe
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2019-08-26 18:06:39 | Re: Procedure support improvements |
| Previous Message | Tom Lane | 2019-08-26 17:46:41 | Re: Proposal: Better generation of values in GENERATED columns. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2019-08-26 18:06:39 | Re: Procedure support improvements |
| Previous Message | Laurenz Albe | 2019-08-26 17:43:45 | Re: Procedure support improvements |