From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Michael Allman <msa(at)allman(dot)ms> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: prepareStatement() |
Date: | 2005-07-23 07:15:50 |
Message-ID: | 42E1EEA6.60407@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Michael Allman wrote:
> Does Postgres's JDBC Connection#prepareStatement(String) method support
> queries that can't be prepared by the backend? (Namely those that are
> not of the SELECT, INSERT, UPDATE, or DELETE variety?)
It supports any query that the backend can parse -- it uses the v3
protocol Parse/Bind messages rather than using the SQL PREPARE statement
so it's not limited to SELECT/INSERT/UPDATE/DELETE.
The main gotcha (just mentioned in my previous email) is that you can
only put parameter placeholders where there is a PARAM terminal in the
server's SQL grammar (i.e. somewhere you could legally put $1, $2, etc)
-O
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2005-07-23 07:21:13 | Re: Timestamp Conversion Woes Redux |
Previous Message | Oliver Jowett | 2005-07-23 07:13:03 | Re: jdbc xa support |