pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dmitriy Igrishin <dmitigr@gmail.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: libpq (PQprepared)
Date: Sun, 29 Aug 2010 10:58:19 -0400
Message-ID: <16891.1283093899@sss.pgh.pa.us> (raw)
In-Reply-To: <AANLkTinh0ZYJeBfGC9hJs0cH0qzPPg1iTFL5njaKqhtU@mail.gmail.com>
References: <AANLkTinh0ZYJeBfGC9hJs0cH0qzPPg1iTFL5njaKqhtU@mail.gmail.com>

Dmitriy Igrishin <dmitigr@gmail.com> writes:
> The description of PQprepare() of libpq
> (http://www.postgresql.org/docs/9.0/static/libpq-exec.html)
> says:

> (But PQprepare is more flexible since it does not require parameter
> types to be pre-specified.)

> But the description of PREPARE
> (http://www.postgresql.org/docs/9.0/static/sql-prepare.html)
> says:

> The data type of a parameter to the prepared statement. If the data
> type of a particular parameter is unspecified or is specified as unknown,
> it will be inferred from the context in which the parameter is used.

> So, PQprepare() is NOT more flexible in this case because PREPARE
> does not require parameters types to be pre-specifies also.

Hmmm ... it was true when written, but is out of date now.  AFAICS
it's sufficient to just remove the parenthetical remark.

			regards, tom lane



view thread (2+ messages)

Message-ID: <16891.1283093899@sss.pgh.pa.us>
Permalink:  ../16891.1283093899@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/16891.1283093899@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, dmitigr@gmail.com
  Subject: Re: libpq (PQprepared)
  In-Reply-To: <16891.1283093899@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox