Hi,
Andrew Dunstan wrote:> I guess my point was really that multi-table indexes might have uses> beyond partitioning.
Aha, now I understand. Thanks for the clarification.
> Say I have two tables, each with a field FKed to a field in a third
> table. I'd like to create the values to be unique across the referring
> tables. Now, there are various tricks that can be played either with
> custom triggers or redundant data to do this, but there's no easy way.
> However, a multi-table unique index would do it for me quite nicely, if
> we could create such a thing.
Maybe going into a similar direction and better think of it as a
multi-table uniqueness constraint, which internally uses multiple,
single-table indexes?
Regards
Markus