Hi guys,
for some reason, any way I try, all the Umlauts get garbled with HDBC 2.1.
HDBC 1.16 worked fine with any backend (ODBC, Sqlite3, ... what have you).
Anybody else had similar problems and knows how to solve this?
Günther
___
Haskell-Cafe
Günther Schmidt wrote:
Hi guys,
for some reason, any way I try, all the Umlauts get garbled with HDBC 2.1.
HDBC 1.16 worked fine with any backend (ODBC, Sqlite3, ... what have you).
Anybody else had similar problems and knows how to solve this?
You need to be more specific, but it is
Guenther Schmidt wrote:
Hi John,
thanks for taking the time. It actually is \252 that turned into
something else because of my email client, damn the thing.
OK, perhaps we have some confusion here.
Are you saying that you entered the Unicode characters directly into
your Haskell source as
On Mon, 2009-05-04 at 11:19 -0500, John Goerzen wrote:
Guenther Schmidt wrote:
Hi John,
thanks for taking the time. It actually is \252 that turned into
something else because of my email client, damn the thing.
OK, perhaps we have some confusion here.
Are you saying that you
Günther Schmidt wrote:
Hi John,
what I just noticed is that *all* strings come back as SqlByteStrings.
That's normal, and pretty much irrelevant, since fromSql takes care of it.
It's documented, even: the SqlByteString is assumed to be in UTF-8, and
is decoded when converted to a String.
It
Günther Schmidt wrote:
Hi John,
I'm afraid so.
If it came back as an SqlString G\252nni then it propably wouldn't
be a problem.
Can you boil this down to a few-line self-contained test program so I
can try it myself? I do have test cases for Unicode stuff and they are
all passing here.
Günther Schmidt wrote:
Am 04.05.2009 um 21:07 schrieb John Goerzen:
Günther Schmidt wrote:
Hi John,
I'm afraid so.
If it came back as an SqlString G\252nni then it propably wouldn't
be a problem.
Can you boil this down to a few-line self-contained test program so I
can try it myself?
At Mon, 04 May 2009 11:19:38 -0500,
John Goerzen wrote:
but instead just typed the umlaut on the keyboard?
If so, that won't work directly -- I think. Maybe somebody can correct
me on this, but my hunch is that would save the umlaut as UTF-8 when you
save the .hs file. Then you will get a