On Fri, 12 Nov 2004, John Hansen wrote:
I miss about UTF-8 :) ltree doesn't supports UTF-8 yet.
ok,. how about all the 'other' characters from us-ascii :
,[EMAIL PROTECTED]&*()_+-=[]{}\|'"?><`~
these 'should' all be valid for the ltxtquery, ltree, and ltree[] types,
except maybe for . which is used
> I miss about UTF-8 :) ltree doesn't supports UTF-8 yet.
ok,. how about all the 'other' characters from us-ascii :
,[EMAIL PROTECTED]&*()_+-=[]{}\|'"?><`~
these 'should' all be valid for the ltxtquery, ltree, and ltree[] types,
except maybe for . which is used as seperator (and maybe . should be
John,
I miss about UTF-8 :) ltree doesn't supports UTF-8 yet.
Oleg
On Thu, 11 Nov 2004, John Hansen wrote:
Oleg,
For example:
The DMOZ topic:
Top/World/Espa??ol/Pa??ses/M?©xico/Referencia/Bibliotecas/Nacionales
select
text2ltree(replace('Top/World/Espa??ol/Pa??ses/M?©xico/Referencia/Bibli
John,
On Thu, 11 Nov 2004, John Hansen wrote:
Hello folks,
It seems that the ltree module does not support the data for which is
was (aparantly) created.
The DMOZ data is encoded in UTF8, but ISALNUM() does not support unicode
characters...
In fact, it does not support any database encoding.
Is the
Hmm,
I don't see the error comes from ltree module, not from 'replace' function.
Also, are you sure your postgresql setup is ok (locale issue).
On Thu, 11 Nov 2004, John Hansen wrote:
Oleg,
For example:
The DMOZ topic:
Top/World/Espa??ol/Pa??ses/M?©xico/Referencia/Bibliotecas/Nacionales
select
te
Oleg,
For example:
The DMOZ topic:
Top/World/Español/PaÃses/México/Referencia/Bibliotecas/Nacionales
select
text2ltree(replace('Top/World/Español/PaÃses/México/Referencia/Bibliotecas/Nacionales','/','.'));
ERROR: syntax error at position 14 near "Ã"
I've also found that topics contain
