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

use of OID.Unknown

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: List <pgsql-jdbc(at)postgresql(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: use of OID.Unknown
Date: 2005-11-08 16:03:08
Message-ID: A9FB7703-8451-4B03-AC70-178F793DF78E@fastcrypt.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
Before we cut an 8.1 stable release, I'd like to revisit the use of  
unknown for strings at a minimum.

Currently the driver exhibits some non-intuitive behaviour.

1) Not using indexes unless the correct type is bound to the  
parameter ( this is intuitive as I write it but many users get  
tripped up ). I'm not sure using unknown for strings would help here
but the other option is using unknown for everything and let the  
backend decide what type to use. This may be an option if we only do  
this when prepareThreshold is 0 since we assume that we won't be  
caching plans anyway.

2) We have broken backward compatibility by changing the behaviour of  
setString.

At a minimum I'd propose we bind strings to unknown.

For or against ?

Dave

Responses

pgsql-jdbc by date

Next:From: Mike ClementsDate: 2005-11-08 16:12:02
Subject: Re: Batch with keygen?
Previous:From: Dave CramerDate: 2005-11-08 15:51:08
Subject: Re: passing parameters to function

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