Re: MERGE and parsing with prepared statements
От | David G. Johnston |
---|---|
Тема | Re: MERGE and parsing with prepared statements |
Дата | |
Msg-id | CAKFQuwZPuwyg=29ssWrO7oeJM4UFpwm3CSmbPMUDc34Y5Uso_Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: MERGE and parsing with prepared statements (Justin Pryzby <pryzby@telsasoft.com>) |
Список | pgsql-hackers |
On Fri, Jul 15, 2022 at 12:40 PM Justin Pryzby <pryzby@telsasoft.com> wrote:
On Fri, Jul 15, 2022 at 12:17:51PM -0700, David G. Johnston wrote:
> On Fri, Jul 15, 2022 at 11:40 AM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> > On 2022-Jul-15, Justin Pryzby wrote:
> >
> > > It seems a bit odd that it's impossible to use merge with prepared statements
> > > without specifically casting the source types (which I did now to continue my
> > > experiment).
> >
> > I have no comments on this. Maybe it can be improved, but I don't know
> > how.
>
> Not tested, but the example prepare command fails to make use of the
> optional data types specification. Using that should remove the need to
> cast the parameter placeholder within the query itself.
What optional data type specification ?
The one documented here:
PREPARE name [ ( data_type [, ...] ) ] AS statement
David J.
В списке pgsql-hackers по дате отправления: