Skip site navigation (1) Skip section navigation (2)

Re: Extended query: prepared statements list?

From: Oliver Fromme <olli(at)lurza(dot)secnetix(dot)de>
To: marcbastin(at)mindspring(dot)com (M(dot) Bastin)
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Extended query: prepared statements list?
Date: 2004-07-15 16:36:31
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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).

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 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

In response to


pgsql-novice by date

Next:From: Oliver ElphickDate: 2004-07-15 16:46:26
Subject: Re: Calling Functions and Stored Procedures
Previous:From: Mark DexterDate: 2004-07-15 15:43:41
Subject: Calling Functions and Stored Procedures

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group