Hey Ann!

> Leyne, Sean wrote:
> >> Don't we have a mechanism for creating transaction ids? Do we

really

> >> need two different ones - one of which uses a generator so it can

be

> >> bumped or reset?
> >
> > The problem with the current transaction id is that it is reset with

a

> > database restore.
>
> 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

restores.

>
> What problem requires that solution?

SOX tracking of all data changes made in the context of a
transaction/session/connection.


Sean