RE: Problem with DB and Char size (2)

2005-01-28 Thread Bayley, Alistair
"TEST", "\195\131" > > 0 is the reference: UTF-8 encoding of an A with a tilde on the top. > 1 is UTF-8 encoding (by Oracle) of an already encoded UTF-8 string > 2a and 2b show that the high byte is stripped: \198\146 is > the UTF-8 encoding of chr(131) > 3 is

Re: Problem with DB and Char size (2)

2005-01-27 Thread Krasimir Angelov
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 withUTF8

Re: Problem with DB and Char size (2)

2005-01-27 Thread John Meacham
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 from my CWStringBasic module, which you can get from here: http://repetae.net/j

Re: Problem with DB and Char size (2)

2005-01-27 Thread robert dockins
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 I

Re: Problem with DB and Char size (2)

2005-01-27 Thread Krasimir Angelov
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, whe