| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Hannu Krosing <hannu(at)2ndquadrant(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: DO ... RETURNING |
| Date: | 2013-06-11 07:30:32 |
| Message-ID: | CAFj8pRBntWdE=vmUbsvj6K1J6fgW_V7BMSojUb3oE-O2D1+yTQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello
>
> The current situation is akin to not being able to use queries
> directly but always requiring you to create a view first and
> then do "select ... from myview"
>
ok
probably we can allow using DO in CTE without impact on other SQL
statements, and for this purpose we need to know returned
TupleDescriptor early.
so I am able accept it, although I am thinking so we are going in
strange direction. We are not able do simply tasks simply (we cannot
execute SQL script on server side simply) :(. But it is not problem of
Hannu design.
other question - can we find some readable and intuitive syntax for DO
parametrization?
Regards
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2013-06-11 07:40:28 | Re: DO ... RETURNING |
| Previous Message | Hannu Krosing | 2013-06-11 07:24:45 | Re: Parallell Optimizer |