|Subject||RE: [Firebird-Architect] Database triggers|
> Leyne, Sean wrote:really
> >> Don't we have a mechanism for creating transaction ids? Do we
> >> need two different ones - one of which uses a generator so it canbe
> >> bumped or reset?a
> > The problem with the current transaction id is that it is reset with
> > database restore.restores.
> That's not a problem - generally, that's a salvation, given that we've
> got 32 bit transaction ids.
> > The generator approach ensures that the ID is unique across
>SOX tracking of all data changes made in the context of a
> What problem requires that solution?