> >I seem to recall someone proposing extending the syntax of the UNIQUE
> >constraints themselves, but there really isn't enough use-case to
> >justify it AFAICS. Especially not when you can always use CREATE
UNIQUE
> >INDEX.
>
> I can always use second unique index. But it's redundant. This problem
is
> related to using nonC locale.
Why do you need both the unique index with varchar_pattern_ops and one
with the default ops?
Because LIKE op don't use index on default ops with non C locale. I found it
on tables of czech communities. Primary key is NUTS - 4..6 numbers. I have
to search values with some prefix -> op Like and on primary key can't to use
std. index.
Pavel
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
