Steel Bank Common Lisp

On Mon, 14 Feb 2005 14:36:41 +0100, R. Mattes wrote:
> I _know_ i've read some blog entry on this problem but can't find it. I
> use an unicode-enabled Xterm but i think i need to set my locale/lang
> environmnet too. But to what?

Seems like setting 'LANG=en_US.UTF-8' will stop sbcl from complaining
about the terminal, but unfortunately i now get the following:



>  TIA Ralf Mattes
> 
> 
> 
> ------------------------------------------------------- SF email is
> sponsored by - The IT Product Guide Read honest & candid reviews on
> hundreds of IT Products from real users. Discover which products truly
> live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
 
 * (select [*] :from 'book :limit 10)

 debugger invoked on a TYPE-ERROR in thread 10476:
   The value #\Ã is not of type BASE-CHAR.
 
 You can type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

 restarts (invokable by number or by possibly-abbreviated name):
  0: [ABORT   ] Reduce debugger level (leaving debugger, returning to toplevel).
  1: [TOPLEVEL] Restart at toplevel READ/EVAL/PRINT loop.
 (SB-KERNEL:HAIRY-DATA-VECTOR-SET 3 "Ausgew0]  BACKTRACE

 0: (SB-KERNEL:HAIRY-DATA-VECTOR-SET 3 "Ausgew1:
 (SB-IMPL::VECTOR-COPY-SEQ* 1 "Ausgewählte Werke")[:EXTERNAL]
 2: (COPY-SEQ 1 "Ausgewählte Werke")[:EXTERNAL] 3:
  ((SB-PCL::FAST-METHOD CLSQL-SYS:DATABASE-QUERY
                         (T CLSQL-POSTGRESQL:POSTGRESQL-DATABASE T T))
    #<unavailable argument>
    #<unavailable argument>
    "SELECT * FROM book LIMIT 10"
    #<CLSQL-POSTGRESQL:POSTGRESQL-DATABASE localhost/rezdb/rezdb OPEN
    {406A4F99}>
    :AUTO
    T)
 4: ("#'(LAMBDA (SB-PCL::.PV-CELL. SB-PCL::.NEXT-METHOD-CALL.
    SB-PCL::.ARG0. ...) (DECLARE #) ...)"
    #<unavailable argument>
    #<unavailable argument>
    "SELECT * FROM book LIMIT 10"
    #<CLSQL-POSTGRESQL:POSTGRESQL-DATABASE localhost/rezdb/rezdb OPEN
    {406A4F99}>
    :AUTO
    T)
   
 .....

Is this a problem of SBCL or do i need to kook into clsql's interna?

 TIA Ralf Mattes

R. Mattes writes:
 > On Mon, 14 Feb 2005 14:36:41 +0100, R. Mattes wrote:
 > > I _know_ i've read some blog entry on this problem but can't find it. I
 > > use an unicode-enabled Xterm but i think i need to set my locale/lang
 > > environmnet too. But to what?
 > 
 > Seems like setting 'LANG=en_US.UTF-8' will stop sbcl from complaining
 > about the terminal, but unfortunately i now get the following:

        You may have to set an environment variable to induce your
database libraries to produce UTF-8 data. For Oracle, something like

        export NLS_LANG=.ALS32UTF8

--- not sure what mechanisms PostgreSQL supports.

On Mon, 14 Feb 2005 16:33:52 +0100, Raymond Wiker wrote:

> R. Mattes writes:
>  > On Mon, 14 Feb 2005 14:36:41 +0100, R. Mattes wrote:
>  > > I _know_ i've read some blog entry on this problem but can't find it. I
>  > > use an unicode-enabled Xterm but i think i need to set my locale/lang
>  > > environmnet too. But to what?
>  > 
>  > Seems like setting 'LANG=en_US.UTF-8' will stop sbcl from complaining
>  > about the terminal, but unfortunately i now get the following:
> 
>         You may have to set an environment variable to induce your
> database libraries to produce UTF-8 data. For Oracle, something like
> 
>         export NLS_LANG=.ALS32UTF8
> 
> --- not sure what mechanisms PostgreSQL supports.

Don't really understand what you mean by this? Off course my Database
_does_ send  UTF8 (as the backtrace shows - that offending character is
the first half of an unicode character). [i've even explicitly set the
client encoding to utf8).

 Thanks RalfD

> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click