Lisp HUG Maillist Archive

Unable to render article 462 because of ":DEFAULT stream decoding error on #<SB-SYS:FD-STREAM for \"socket 192.168.43.216:64974, peer: 116.202.254.214:119\" {1003792D33}>: the octet sequence #(246 228 252 32) cannot be decoded." error

Re: Umlauts and CommonSQL

----- Original Message -----
From: Friedrich Dominicus <frido@q-software-solutions.com>
To: <lisp-hug@xanalys.com>
Sent: Thursday, July 11, 2002 6:37 PM
Subject: Umlauts and CommonSQL


| Can anyone tell me how to enable CommonSQL with ODBC to accept content
| with Umlauts?
|
| I got this error message while trying to access such a table:
| CL-USER 5 > (sql:query "select * from foo_test")
|
| Error: External format :ASCII got error reading #<Pointer to type
(:UNSIGNED :CHAR) = #x08156340> at position 0: Non-ASCII code 246.
|   1 (abort) Return to level 0.
|   2 Return to top loop level 0.
|
|...snip...|

If your were on Windows, I would suggest checking the value of
*default-character-element-type* and call

    (lw:set-default-character-element-type 'lw:simple-char)

if needed, i.e. if base-char were the default.

I had to do so in LWW 4.1 to fetch data via ODBC. Maybe LWL 4.2 has the
same.
---
Sincerely,
Dmitri Ivanov
www.aha.ru/~divanov



Re: Umlauts and CommonSQL

Unable to parse email body. Email id is 466

Re: Umlauts and CommonSQL

Unable to parse email body. Email id is 464

Re: Umlauts and CommonSQL

Unable to parse email body. Email id is 465

Re: Umlauts and CommonSQL

davef@xanalys.com writes:

>    Can anyone tell me how to enable CommonSQL with ODBC to accept content
>    with Umlauts?
> 
> See the Knowledgebase at the Xanalys
> website. http://www.xanalys.com/software_tools/support/
I'm sorry than for answereing a FAQ question. Well I was offline the
last few days and it has not come to my mind to check out the
Knowledgebase. 

Thanks anyway.

Regards
Friedrich


Updated at: 2020-12-10 09:02 UTC