I had the same problem. I solved it by doing query using the pattern
matching operator ~*.
I paste an example query
select id_edb,transcription from epigraph where transcription ~* 'εἰρήνῃ'
and it works
best
Fabio
Tom, Greg,
Please accept my considerable apologies. The fault was my own program that
loaded metadata into the text column, metadatafulltext. My reason (not a
sufficient excuse!) for overlooking the problem is that the Unicode is
invisible in psql windows, therefore it was not a simple matter
Thanks, Tom and Greg, for all your help. I agree that Redhat 9 is a bit
creaky and that we here should upgrade. In the meantime I will put together a
tiny test case that will reproduce the problem (at least on my platform).
Ben
In message <[EMAIL PROTECTED]> Tom Lane <[EMAIL PROTECTED]>
writ
Gregory Stark <[EMAIL PROTECTED]> writes:
> "Tom Lane" <[EMAIL PROTECTED]> writes:
>> Hmph, nothing strange-looking there. I tried to reproduce the problem
>> here, without success. Now I was using 8.1.10 on Linux (I gather your
>> platform is not Linux from the spelling of the locale names)
> R
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Benjamin Weaver <[EMAIL PROTECTED]> writes:
>> Postgres 8.1.4
>> server_encoding UTF8
>> lc_collate en_GB.UTF-8
>> lc_ctype en_GB.UTF-8
>
> Hmph, nothing strange-looking there. I tried to reproduce the problem
> here, without success. Now I was using 8
Benjamin Weaver <[EMAIL PROTECTED]> writes:
> I AM in fact running the db on Linux. Redhat 9. Are the encoding parameters
> wrong for Linux?
Hmm ... RH 9 is awfully old. It's at least conceivable that you're
getting bit by some glibc bug. However, if these are just plain LIKE
calls and not ILI
Dear Greg, Tom,
I AM in fact running the db on Linux. Redhat 9. Are the encoding parameters
wrong for Linux?
I am sending the queries via JDBC from a windows machine. But I have also
gotten the same results via psql when sending the queries from one local redhat
9 box to the redhat 9 database
"Benjamin Weaver" <[EMAIL PROTECTED]> writes:
> Tom,
>
> Thanks. I am running:
>
> Postgres 8.1.4
> server_encoding UTF8
> lc_collate en_GB.UTF-8
> lc_ctype en_GB.UTF-8
Hm, I wonder what the en_GB locale on your machine does when it sees
characters unused in English such as Greek characters.
Benjamin Weaver <[EMAIL PROTECTED]> writes:
> Postgres 8.1.4
> server_encoding UTF8
> lc_collate en_GB.UTF-8
> lc_ctype en_GB.UTF-8
Hmph, nothing strange-looking there. I tried to reproduce the problem
here, without success. Now I was using 8.1.10 on Linux (I gather your
platform is not Linux
Tom,
To be more precise, the mixed queries "fail" in that they return hits of 0
rows, when they should return more than 0 rows.
Ben
In message <[EMAIL PROTECTED]> Tom Lane <[EMAIL PROTECTED]>
writes:
> Benjamin Weaver <[EMAIL PROTECTED]> writes:
> > I have the following problem: a compound s
Tom,
Thanks. I am running:
Postgres 8.1.4
server_encoding UTF8
lc_collate en_GB.UTF-8
lc_ctype en_GB.UTF-8
Ben
In message <[EMAIL PROTECTED]> Tom Lane <[EMAIL PROTECTED]>
writes:
> Benjamin Weaver <[EMAIL PROTECTED]> writes:
> > I have the following problem: a compound search, involving
Benjamin Weaver <[EMAIL PROTECTED]> writes:
> I have the following problem: a compound search, involving 2 wildcarded
> character search terms, in which one search term consists of Latin characters
> and the other, of UTF-8 unicode Greek characters, fails. This is strange,
> because similar searc
Dear all,
I have the following problem: a compound search, involving 2 wildcarded
character search terms, in which one search term consists of Latin characters
and the other, of UTF-8 unicode Greek characters, fails. This is strange,
because similar searches in which both terms are either unicod
13 matches
Mail list logo
