Hello,
I created a new database with a single table + index:
CREATE TABLE "Basic"
(
"Name" VARCHAR(50) COLLATE "HEB" NOT NULL,
"Color" VARCHAR(50) COLLATE "HEB",
CONSTRAINT "PK" PRIMARY KEY ("Name")
)
VERSION 1
UNENCRYPTED
INDEX PAGE SIZE 4096
BLOB BLOCK SIZE 512
MAX ROW BUFFER SIZE 32768
MAX INDEX BUFFER SIZE 65536
MAX BLOB BUFFER SIZE 32768

Filled 4 rows (csv export):
"îëúá","éøå÷"
"îëåðä","àãåí"
"îëåðéú","ëçåì"
"øëáú","àãåí"

Now when I set the filter: name = 'îë*' I get 2 rows instead of 3! If I drop
the constraint it works. If I create a view with the corresponding sql it
also works.

Any ideas?

Felix.

This still happens in 1.04.
I'm sure it's an index issue - if I set the filter to case-insensitive,
which causes to not use the index, I get correct results.

Felix.

"Felix Gartsman" <garisman@netvision.net.il> wrote in message
news:A8E2087F-6608-40C0-9A22-C53CB485EBAB@news.elevatesoft.com...
> Hello,
> I created a new database with a single table + index:
> CREATE TABLE "Basic"
> (
> "Name" VARCHAR(50) COLLATE "HEB" NOT NULL,
> "Color" VARCHAR(50) COLLATE "HEB",
> CONSTRAINT "PK" PRIMARY KEY ("Name")
> )
> VERSION 1
> UNENCRYPTED
> INDEX PAGE SIZE 4096
> BLOB BLOCK SIZE 512
> MAX ROW BUFFER SIZE 32768
> MAX INDEX BUFFER SIZE 65536
> MAX BLOB BUFFER SIZE 32768
>
> Filled 4 rows (csv export):
> "îëúá","éøå÷"
> "îëåðä","àãåí"
> "îëåðéú","ëçåì"
> "øëáú","àãåí"
>
> Now when I set the filter: name = 'îë*' I get 2 rows instead of 3! If I
> drop the constraint it works. If I create a view with the corresponding
> sql it also works.
>
> Any ideas?
>
> Felix.

Felix,

<< Now when I set the filter: name = 'îë*' I get 2 rows instead of 3! If I
drop the constraint it works. If I create a view with the corresponding sql
it also works. >>

I'll have to look into this further before I can comment, but I suspect that
the issue has something to do with the way the collation is working.

--
Tim Young
Elevate Software
www.elevatesoft.com

Felix,

<< Filled 4 rows (csv export):
"îëúá","éøå÷"
"îëåðä","àãåí"
"îëåðéú","ëçåì"
"øëáú","àãåí" >>

I'm getting a primary key violation on the last row (Windows XP English-US).
I hope that I'm doing this correctly - I'm using the value on the right as
the Name value, and the value on the left as the Color value.

--
Tim Young
Elevate Software
www.elevatesoft.com

Felix,

BTW, I'm assuming that this is using the Unicode version of EDB ?

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:8DB08DAB-9656-43BF-87EA-8BA387D54DA7@news.elevatesoft.com...
> Felix,
>
> << Filled 4 rows (csv export):
> "îëúá","éøå÷"
> "îëåðä","àãåí"
> "îëåðéú","ëçåì"
> "øëáú","àãåí" >>
>
> I'm getting a primary key violation on the last row (Windows XP
> English-US). I hope that I'm doing this correctly - I'm using the value on
> the right as the Name value, and the value on the left as the Color value.

The violation is because the columns are wrong on import, although you do
describe the order right. Maybe your newsreader reversed it. "îëúá" is in
the Name column.
You need to set Hebrew as the default codepage, or it may work differently.

Felix.

No, ANSI version with Windows Vista Ultimate with English UI, but Hebrew as
default non-Unicode codepage.

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:289FCF4E-868C-4A89-A00F-F495F25C7FBC@news.elevatesoft.com...
> Felix,
>
> BTW, I'm assuming that this is using the Unicode version of EDB ?
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Felix,

<< No, ANSI version with Windows Vista Ultimate with English UI, but Hebrew
as default non-Unicode codepage. >>

Thanks, I've solved the problem now.

--
Tim Young
Elevate Software
www.elevatesoft.com