Re: Extended query: prepared statements list? - Mailing list pgsql-novice

From Oliver Fromme
Subject Re: Extended query: prepared statements list?
Date
Msg-id 200407151636.i6FGaVmp017673@lurza.secnetix.de
Whole thread Raw
In response to Extended query: prepared statements list?  ("M. Bastin" <marcbastin@mindspring.com>)
Responses Re: Extended query: prepared statements list?  ("M. Bastin" <marcbastin@mindspring.com>)
List pgsql-novice
M. Bastin wrote:
 > [...]
 > The fact that you can work with parameters opens up a whole new
 > dimension as well, e.g.:
 >
 >     SELECT * FROM population WHERE age > $1 AND age < $2;
 >
 > I only wish there were more documentation about the extended query
 > language.  All I've found on the whole internet would hold on 2 to 3
 > printed pages.  Did I miss something?)

I'm not sure what exactly you are missing, but the page
documenting the PREPARE statement (in the official Postgres
docs) pretty much says it all.  Also, it's easy to find
(Docs -> Reference -> SQL Commands -> PREPARE).

http://www.postgresql.org/docs/7.4/static/sql-prepare.html

However, maybe we're actually talking about completely
different things -- in that case I would like to know what
you are talking about.  :-)

Best regards
   Oliver

--
Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.

 > Can the denizens of this group enlighten me about what the
 > advantages of Python are, versus Perl ?
"python" is more likely to pass unharmed through your spelling
checker than "perl".
        -- An unknown poster and Fredrik Lundh

pgsql-novice by date:

Previous
From: "Mark Dexter"
Date:
Subject: Calling Functions and Stored Procedures
Next
From: Oliver Elphick
Date:
Subject: Re: Calling Functions and Stored Procedures