| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Shay Rojansky <roji(at)roji(dot)org> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, daniel(at)manitou-mail(dot)org, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Stored procedures and out parameters |
| Date: | 2018-08-02 16:16:49 |
| Message-ID: | CAB=Je-GDO7UnT=oE0VU8avfjCEDtn691paua+rSXj-YEw05nmg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Shay>Npgsql currently always sends a describe as part of statement
execution (for server-prepared messages the describe is done only once, at
preparation-time). Vladimir, are you doing things differently here?
The same thing is for pgjdbc. It does use describe to identify result row
format.
However, "CALL my_proc()" works just fine with current git master for both
simple and extended protocol.
The missing part is "invoke functions via CALL statement".
Vladimir
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-08-02 16:23:41 | Fallout from PQhost() semantics changes |
| Previous Message | Laurenz Albe | 2018-08-02 16:08:27 | Re: Problem during Windows service start |