"Kevin Grittner" <[EMAIL PROTECTED]> writes:
> What happens if the timestamp of the commit is an exact match for the
> timestamp of the next transaction start? What is the resolution of
> the time sampling?
It's not done via timestamps: rather, each transaction takes a census
of the transaction X
"Kevin Grittner" <[EMAIL PROTECTED]> writes:
> The problem is this: a single thread is submitting database updates through
> a middle tier which has a pool of connections. There are no guarantees of
> which connection will be used for any request. Each request is commited as
> its own databas
