Whatever database you deal with - never rely on timestamps, they are not for
multi-user/process environment. FB has nothing wrong in it.

A correct usage of Serialized, Read commited, Repeatable Read transaction
should solve your issue. In your case: Repeatable Read seems to be a
solution.

At extreme, you may serialize your SQL yourself on some "Ordered ID
Generator". Performance would suffer. But then you may assign unique and
ordered ID for every record and be sure that id1<id2 means time1<time2.
Anyway, this extreme hardly needed for you, just an option.








[Non-text portions of this message have been removed]