Re: Parsing speed (was Re: pgstats_initstats() cost)

> > Wait just a minute!  phpPgAdmin would love to be able to 'parse' arbitrary
> > sql entered by the user to separate semi-coloned queries, identify various
> > types of queries, etc.  What would a Parse call allow us to do?
>
> Hm.  I was about to say "very little that you can't do with a PREPARE",
> but if you don't want to even count semicolons then Parse would be
> distinctly safer.  For example if the string is
>     SELECT * FROM foo; UPDATE foo SET ...
> then sticking a PREPARE in front would not have the desired effect ---
> but sending it in a Parse message would result in a syntax error.
> Not sure if that helps you get to your goal though.

What do you actually get back from a Parse request?

Chris