From: | Chris Holmes <cholmes(at)openplans(dot)org> |
---|---|
To: | <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | charSet with Jdbc3PoolingDataSource |
Date: | 2003-08-12 20:36:41 |
Message-ID: | Pine.LNX.4.33.0308121548000.10599-100000@lime1.limewire.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hi, I'm looking to use connection pooling with Postgresql jdbc, but one of
my requirements is the use of the charSet param. As far as I can tell it
is not supported in Jdbc3PoolingDataSource, I downloaded 7.4beta1 to check
and didn't find anything there. Are there any plans to add this
capability, or reasons as to why it is not in the jdbc3 code? Looking
through this list I see that users should probably just create their db's
with the correct language, and everything should work a lot better, but
many of my users already have their installations up and running, and
currently rely on the charSet param. I would prefer to not just drop that
support when I move to pooled connections, forcing them to redo their dbs.
Looking through the code it doesn't seem that difficult to add, just add a
setCharSet method to jdbc2.optional.BaseDataSource, have getUrl() use the
charSet, and have jdbc2.optional.PoolingDataSource override with the
method with an IllegalStateException similar to its other overrides. Or
is there more to be done? This is the first time I've really looked at
the code. Apologies if this has been discussed on the list before, but in
my search of the archives I found nothing. I'm willing to put in a bit of
devel time if needed to fix this problem, as it'll make my international
users happy.
thanks,
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2003-08-12 21:38:32 | Re: Character Decoding Problems |
Previous Message | Paul Thomas | 2003-08-12 14:50:37 | Re: FW: FW: pgsql - query |