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

Re: Pass column name in preparedstatement

From: Antony Paul <antonypaul24(at)gmail(dot)com>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Pass column name in preparedstatement
Date: 2005-02-16 04:14:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
The one glitch I have with 7.3.3 is with functional index and it is
solved in 8.x only. But the client is not ready to upgrade to 8.x
series until it ages 4-6 months. So I dont find any use in upgrading.
I have to consider the work invloved in upgrading.

Antony Paul

On Wed, 16 Feb 2005 11:59:56 +1300, Oliver Jowett <oliver(at)opencloud(dot)com> wrote:
> Antony Paul wrote:
> > In 7.3.3 is there any use in using PreparedStatement since the columns
> > may change for each query.
> It depends on your application; are there non-column-name parameters? If
> so, using PreparedStatement still gives you the benefit that you do not
> have to escape those parameters by hand.
> Under 7.3.x there's no real performance benefit to reusing
> PreparedStatements, as the v3 protocol (supporting server-side query
> parameterization and reuse) was only introduced in 7.4. Under 7.4 or
> 8.0, there is some scope for improved performance if you reuse
> PreparedStatements. As your query strings are changing, you may want to
> have a cache to preserve a PreparedStatement for frequently used queries.
> You really should upgrade if you're still using 7.3.3, at least to the
> latest 7.3.x.
> -O

In response to


pgsql-jdbc by date

Next:From: Oliver JowettDate: 2005-02-16 05:26:47
Subject: Re: Pass column name in preparedstatement
Previous:From: Oliver JowettDate: 2005-02-15 22:59:56
Subject: Re: Pass column name in preparedstatement

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