| From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
|---|---|
| To: | Yury Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Subject: | Re: NOT EXIST for PREPARE |
| Date: | 2016-03-22 12:35:23 |
| Message-ID: | CAFcNs+p-tfWco3zmO+Awkci4-NveTMAgFMeM1_RvzHiP837y1Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Em terça-feira, 22 de março de 2016, Yury Zhuravlev <
u(dot)zhuravlev(at)postgrespro(dot)ru> escreveu:
> Hello hackers.
>
> Do I understand correctly the only way know availability PREPARE it will
> appeal to pg_prepared_statements?
> I think this is not a good practice. In some cases, we may not be aware of
> the PREPARE made (pgpool). Moreover, it seems popular question in the
> Internet:
> http://stackoverflow.com/questions/1193020/php-postgresql-check-if-a-prepared-statement-already-exists
>
>
+1
> What do you think about adding NOT EXIST functionality to PREPARE?
>
>
I think you meant IF NOT EXISTS, right?
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog: http://fabriziomello.github.io
>> Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
>> Github: http://github.com/fabriziomello
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2016-03-22 12:37:24 | Re: multivariate statistics v14 |
| Previous Message | Michael Paquier | 2016-03-22 12:28:32 | Re: WIP: Upper planner pathification |