Greetings,

I've found some problems to handle the directional marks (i.e. for arabic
charset in UNICODE 0x200e and 0x200f). As I've exported the db from Microsoft
SQL 7.0 there were so many directional marks even inside words (i.e. "foo"
-> "f(200e)oo"). This probably is due to an external program which was used
to fill the db with values.

Directional marks are not shown in the client browser but for PostgreSQL
is a character. This is a problem when I try to SELECT the db:

SELECT * FROM table WHERE field = "foo";

If in "table" there is a record which contais "foo" as value for "field",
but it has a directional mark in it (i.e.: "f(200e)oo"), I can't get any
result.

The only way to fix the problem is to remove any directional mark occurrence,
or to make PostgreSQL ignore that kind of characters during UNICODE queries.

What do you think about it?
Thx.

---
Nhan NGO DINH



__________________________________________________________________
Tiscali Ricaricasa
la prima prepagata per navigare in Internet a meno di un'urbana e
risparmiare su tutte le tue telefonate. Acquistala on line e non avrai
nessun costo di attivazione né di ricarica!
http://ricaricasaonline.tiscali.it/




Mon, 16 Sep 2002 14:46:03 +0200
nngodinh@tiscali.it
directional marks
nngodinh@tiscali.it writes:

> The only way to fix the problem is to remove any directional mark occurrence,
> or to make PostgreSQL ignore that kind of characters during UNICODE queries.
>
> What do you think about it?

Either remove the directional marks or consistently use them in all your
queries (or use wildcards to paint over the difference).  The directional
mark characters aren't just for amusement -- they contain real information
so they cannot be ignored.

-- 
Peter Eisentraut   peter_e@gmx.net



Mon, 16 Sep 2002 19:25:30 +0200 (CEST)
Peter Eisentraut <peter_e@gmx.net>
Re: directional marks