> I thought it was working fine, until I tryed to find information about a
> channel called #espa?a. For our surprise the bot told "No records found for
> #espa?a". So I got curious and made other tests... it doesn't works for any
> channels with chars like ? in the name.
> Well... another interesting notes: I can see information about that kind of
> channel name using a third part PHP nterface. Current server encoding is
> 'SQL_ASCII'. (I'm not familiar with that... but some guys told that it may
> be usefull).
Two possible causes come to mind. Hope this helps.
(1) If your database encoding is SQL_ASCII, you will have problems storing
and retrieving non-ASCII characters from CHAR, VARCHAR, and TEXT fields.
Your database encoding should be something more appropriate to your locale,
perhaps "Latin1" or "UNICODE". This is especially important with Tcl
interfaces, which send and expect UTF-8 (Unicode) encoded characters
to/from PostgreSQL. PostgreSQL will handle the conversion between Tcl and
your database encoding, unless the database encoding is SQL_ASCII.
(2) You have:
set query [pg_exec $conexao "SELECT * FROM channels WHERE \
lower(name)='[string tolower [lindex $rest 0]]'";]
It would be nice to think that SQL lower() gives the same results as Tcl's
[string tolower] on non-ASCII characters, but I am a skeptic, and would
want to prove it with some tests. Perhaps it does work, but only if the
database encoding is right. Or maybe it is better not to mix server-side
and client-side case mangling.
In response to
pgsql-interfaces by date
|Next:||From: Kuba Ouhrabka||Date: 2005-08-02 08:40:23|
|Subject: ecpg: arrays and nulls|
|Previous:||From: Paulo Ricardo Stradioti||Date: 2005-07-31 07:16:07|
|Subject: Problem With TCL|