From: | Jochem van Dieten <jochemd(at)oli(dot)tudelft(dot)nl> |
---|---|
To: | Barry Lind <barry(at)xythos(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: [JDBC] Prepared statement performance... |
Date: | 2002-09-27 11:50:18 |
Message-ID: | 3D9445FA.3050203@oli.tudelft.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-jdbc |
Barry Lind wrote:
>
> Your first option is what has been implemented. In 7.3 the server now
> supports 'prepare <name> as <sql>' and 'execute <name>' (and variants
> for passing bind variables). The jdbc driver also now has a method on
> org.postgresql.PGStatement.setUseServerPrepare(true) to enable the the
> use of server side prepared statements (so you can cast your Statement
> object to an org.postgresql.PGStatement object and enable the
> functionality for a specific statement).
[..]
> It is for the reasons above that the developer needs to explicitly turn
> on the use of server side prepared statements when it makes sense to do so.
How would the developer do that? With the front-end I am working with
(ColdFusion MX) I have very little control over the actual calls to the
driver. I can make CF MX use createStatement() or prepareStatement() but
that is all the control I have. And the only way to send parameters to
the driver would be through a JDBC URL.
Would that enable me to use prepared statements for real or not?
Jochem
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Gelbrich | 2002-09-27 11:57:58 | Re: Feature comparison between Postgresql, Oracle and Mysql ? |
Previous Message | Andriy Tkachuk | 2002-09-27 11:46:43 | Re: query speed depends on lifetime of frozen db? |
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2002-09-27 11:57:49 | [Fwd: [HACKERS] [ANNOUNCE] PQNotify java listen / notify hack] |
Previous Message | Dave Cramer | 2002-09-27 11:29:46 | Re: [JDBC] Prepared statement performance... |