Right, but does the pattern_ops one have to be unique?
Sorry, I don't uderstand
And if it does, do you need the normal unique constraint as well?
Sometime yes. It's about using natural or generated unique values.
I looked to source code and I propouse syntax:
CREATE TABLE name ..
colname t
> >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 p
Why would you need it?
I can't to use unique index for like_op without setting opclass, because I
have to use czech locale. I can create second index, but then I have two
equal indexes. Example:
number | description
000102 blabla bla
000103 fooo
number: varchar primary key.
Someti
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> There isn't possibility change opclass for generated UNIQUE indexes.
Why would you need it?
> USING INDEX [TABLESPACE ..] [OPCLASS ..]
This is unworkable --- consider a table with more than one unique
constraint and/or multiple-column constraints.
Hello
There isn't possibility change opclass for generated UNIQUE indexes. I found
syntax for CREATE TABLE command USING INDEX TABLESPACE ..., This form can be
enhanced to
USING INDEX [TABLESPACE ..] [OPCLASS ..]
What do you think about it?
Regards
Pavel Stehule
___
