CLSQL on Windows BABEL situation

From: ·········@yahoo.com
Subject: CLSQL on Windows BABEL situation
Date: Fri, 31 Oct 2008 22:43:45 +0000
Message-ID: <26753679-8abe-49fa-bf97-82e25d8a8579@g17g2000prg.googlegroups.com>

CLSQL on windows with CLISP looks to be working fine... Most queries
hitting againt a SQL Server
backend return results as expected. However, I have run into this
problem when trying to select
rows from a certain table:

illegal: UTF-8 character starting on position 7.
  [Condition of type BABEL-ENCODINGS-INVALID-UTF8-STARTER-BYTE]

(Note, with Lispworks  and the same CLSQL, I don't have this problem--
the BABEL query
 works fine)

I am wondering about what might be causing the BABEL error to occur on
CLISP, and if there is
an easy fix available.

(Note that i have the following  modules referenced in my CLSQL
initialization file:

trivial-features_0.3
alexandria
babel_0.3.0
uffi-1.61.
cffi_0.10.3
clsql-4.0.3)


Any thoughts?

Re: CLSQL on Windows BABEL situation Pascal Bourguignon
- Re: CLSQL on Windows BABEL situation ·········@yahoo.com

From: Pascal Bourguignon
Subject: Re: CLSQL on Windows BABEL situation
Date: Sat, 01 Nov 2008 01:43:32 +0000
Message-ID: <490bb444$0$9221$426a74cc@news.free.fr>

·········@yahoo.com wrote:
> CLSQL on windows with CLISP looks to be working fine... Most queries
> hitting againt a SQL Server
> backend return results as expected. However, I have run into this
> problem when trying to select
> rows from a certain table:
> 
> illegal: UTF-8 character starting on position 7.
>   [Condition of type BABEL-ENCODINGS-INVALID-UTF8-STARTER-BYTE]
> 
> (Note, with Lispworks  and the same CLSQL, I don't have this problem--
> the BABEL query
>  works fine)
> 
> I am wondering about what might be causing the BABEL error to occur on
> CLISP, and if there is
> an easy fix available.

A quick-and-dirty fix: In clisp, don't use charset:utf-8, but make your 
own encoding that substitutes or remove illegal input codes. (See the 
Implementation Notes about ext:make-encoding).

The correct fix: specify the encoding really use by the database, where 
it is needed to be specified.


-- 
__Pascal Bourguignon__
http://www.informatimago.com

From: ·········@yahoo.com
Subject: Re: CLSQL on Windows BABEL situation
Date: Sat, 01 Nov 2008 07:08:52 +0000
Message-ID: <2f46933d-a50c-4230-8d13-d87b039fea35@q30g2000prq.googlegroups.com>

On Oct 31, 9:43 pm, Pascal Bourguignon <····@informatimago.com> wrote:
> ·········@yahoo.com wrote:
> > CLSQL on windows with CLISP looks to be working fine... Most queries
> > hitting againt a SQL Server
> > backend return results as expected. However, I have run into this
> > problem when trying to select
> > rows from a certain table:
>
> > illegal: UTF-8 character starting on position 7.
> >   [Condition of type BABEL-ENCODINGS-INVALID-UTF8-STARTER-BYTE]
>
> > (Note, with Lispworks  and the same CLSQL, I don't have this problem--
> > the BABEL query
> >  works fine)
>
> > I am wondering about what might be causing the BABEL error to occur on
> > CLISP, and if there is
> > an easy fix available.
>
> A quick-and-dirty fix: In clisp, don't use charset:utf-8, but make your
> own encoding that substitutes or remove illegal input codes. (See the
> Implementation Notes about ext:make-encoding).
>
> The correct fix: specify the encoding really use by the database, where
> it is needed to be specified.
>
> --
> __Pascal Bourguignon__http://www.informatimago.com

Pascal,

I set binding CFFI:*DEFAULT-FOREIGN-ENCODING* to :ISO-8859-1.

and that fixed my problem.

Thanks,

Nelson Marcelino