Vlad,

>>The solution that NuoDB implemented is to keep
>> a sparse bitmap of the db-keys of
>> the inserted records and not reinsert them when they come back from
>> the select.
>
>  But this way updates and deletes are not addressed. Probably NuoDB's
> implementation is more complex than just bitmap of inserted record
> numbers and really addressed all cases of unstable cursor...

The goal was not to make all cursors stable, but just to avoid the infinite
loop of insert ... select. I'll have to create some new bug reports for NuoDB
reflexive update and delete. Jim's not going to be pleased.

>> It's possible to do the same thing using the information in the
>> savepoint undo list, I think, and maybe Firebird implemented that after 2.0.
>
>  Yes, it is done in FB3 (still pre-alpha)
>

Excellent. One 30 year old bug bites the dust.

Cheers,

Ann