Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Message-ID: <40CD96DA.4020208@cologne-systems.de>
Date: Mon, 14 Jun 2004 14:15:22 +0200
From: Markus Krogemann <markus.krogemann@cologne-systems.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.6) Gecko/20040113
MIME-Version: 1.0
To: Jakarta Commons Users List <commons-user@jakarta.apache.org>
Subject: [dbcp] limitation on size of varchar in conjunction with sybase?
References: <LAEMKBGKGGDLCMAKICOPMEGLEPAA.martinc@apache.org>
In-Reply-To: <LAEMKBGKGGDLCMAKICOPMEGLEPAA.martinc@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Dear list

I am having trouble with a PoolingDriver implementation in conjunction 
with sybase (ASE 12.5, jconnect 5.5) and dbcp 1.1.
I know that in order to successfully read varchars with lengths greater 
than 255, i need to set a property in the jconnect driver like this:

sybdriver.setVersion(com.sybase.jdbcx.SybDriver.VERSION_LATEST)

This works ok when i don't use a db pool but just a single "hand-made" 
connection.

However, when i use a PoolingDriver implementation i can only get 255 
chars from a varchar that contains more than 255 chars. Is there any 
limitation in PoolingDriver that could cause that? I know, it's 
unlikely, but i thought i'd ask before looking much further. Could it be 
that the setVersion call stays without effect in the presence of 
PoolingDriver?

Also: Have other readers had similar problems and - better still - a 
solution?

Best regards,
Markus


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org