On Tue, Jun 11, 2013 at 09:30:32AM +0200, Pavel Stehule wrote:
> 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?
The thing I'm thinking of where this does something we don't yet do is
in the realm of access control, e.g. allowing people to use DO rather
than giving them DDL permission to create temporary functions.
Is this what you have in mind? What other things?
Cheers,
David.
--
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fetter@gmail.com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
