Daniel Noll wrote:
Ah. I was making the assumption that the indexes were implemented
"properly." For instance, an index should keep a certain amount in
memory in order to have a reasonable chance of running quickly. So the
max and min should already be in-memory.
I take it that Derby doesn't do this?
The column doesn't necessarily have to have an index or even be unique.
An insert will only fail when there's a unique constraint on the
column and the sequence generator returns a value that's already been
used.
