Re: Indexed Organized Tables

bdbafh_at_gmail.com wrote:

> what version of Oracle, as the type TIMESTAMP should have a much finer
> resolution than one second, not that centiseconds or milliseconds would
> eliminate the race condition anyways.
>
> use a sequence to generate a numeric unique identifier and add that
> column to the primary key - populate in the insert trigger if the
> sequence.nextval is not included in the insert statement.
> hth.
>
> -bdbafh
>

Well, we are actually not using the TIMESTAMP value (sorry), but a simple DATE column. As such a race condition is much more likely.

So I take it then that it's not possible to create an IOT without a unique primary key?

The sequence idea sounds good, but isn't that still going to slow down the index, having those identifiers in there also?

Thanks! Received on Mon Jan 10 2005 - 14:37:34 CST