Subject: R: Problem with DB and Char size (2)
This is exactly what happens:
(btw, the same thing happens in Python, so the trouble must
be in the Oracle odbc driver. But this is also what happens
today to any Haskell business application which connects to
Oracle, as - to my knowledge
Oops... I hit the wrong key, sending a partial post. Sorry :)
Again:
I have a problem with strings and unicode chars, when writing slq statements on
Oracle ODBC driver through HSQL.
I'm writing here because I suspect that a fix could come from writing 8 bit
strings, if it is possible somehow.
I have a problem with strings and unicode chars, when writing slq statements on
Oracle ODBC driver through HSQL.
I'm writing here because I suspect that a fix could come from writing 8 bit
strings, if it is possible somehow.
I'm sorry, the problem is very deep into it's context, and I know it's
HSQL uses withCString internally. withCString strips the higher order
bytes from Char.
On Thu, 27 Jan 2005 15:11:38 +0100, Santoemma Enrico
[EMAIL PROTECTED] wrote:
Oops... I hit the wrong key, sending a partial post. Sorry :)
Again:
I have a problem with strings and unicode chars, when
As I haven't found how to force the driver not to strip the byte, and also I
don't like to convert data two times, I'd try to send 8 bit strings, but don't
know how.
Is Word8 a solution? If it is, what is the contstructor?, as w = W8# 1 doesn't
compile.
I'm weak on low level Haskell. Where do
On Thu, 27 Jan 2005 06:34:40 -0800, John Meacham [EMAIL PROTECTED] wrote:
On Thu, Jan 27, 2005 at 04:23:52PM +0200, Krasimir Angelov wrote:
HSQL uses withCString internally. withCString strips the higher order
bytes from Char.
You should be able to replace withCString with withUTF8String
]
Inviato: giovedì 27 gennaio 2005 15.41
A: glasgow-haskell-users@haskell.org
Oggetto: Re: Problem with DB and Char size (2)
On Thu, 27 Jan 2005 06:34:40 -0800, John Meacham [EMAIL PROTECTED] wrote:
On Thu, Jan 27, 2005 at 04:23:52PM +0200, Krasimir Angelov wrote:
HSQL uses withCString
Santoemma Enrico [EMAIL PROTECTED] writes:
The problem is: Oracle ODBC driver expects, at least under Windows,
UCS-2 strings. Then, if the DB is set to UTF-8, it converts the string
into UTF-8. I'm using HSQL to access ODBC.
Isn't UCS-2 the old 16-bit Unicode representation? So that