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

Re: Problems with charsets, investigated...

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: alexandre(dot)aufrere(at)inet6(dot)fr
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Problems with charsets, investigated...
Date: 2004-08-08 11:57:02
Message-ID: 4116150E.2080302@opencloud.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
Alexandre Aufrere wrote:

>>Can you dump out the *characters* of the problem Strings you get from 
>>the driver, one character at a time, and see what numeric values you're 
>>getting and whether they are the right UTF-16 values you expect? i.e.
>>
>>  for (int i = 0; i < str.length(); ++i) {
>>   System.out.println(" offset " + i + " value " + (int)str.charAt(i));
>>  }
>>
>>Can you provide a pg_dump (LATIN1 encoding I assume) plus sample 
>>testcase that shows off the problem?
> 
> 
> well, i'll investigate more tomorrow, at work, and try to set up a simple 
> test program to try to understand deeper what's going on. 
> currently, we see the problem by doing a debug output (simply a 
> System.out) from Enhydra's DODS (which is the relational-object layer). 
>>From what i've seen in DODS (maybe, though, i didn't dig enough), DODS 
> does not manipulate Strings coming from the JDBC driver when they are of 
> type VARCHAR, therefore it shouldn't be the source of the problem. 
> about the charAt thing, it is as well not correct, i tried...

Can you show me the charAt output for some sample data that shows the 
problem? (and the corresponding string as it's stored in the database)

-O

In response to

Responses

pgsql-jdbc by date

Next:From: Oliver JowettDate: 2004-08-08 12:00:57
Subject: Re: executing batch select queries
Previous:From: Alexandre AufrereDate: 2004-08-08 08:18:54
Subject: Re: Problems with charsets, investigated...

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