You could very well be right.
We are using JPA under Hibernate, using container managed transactions. So T1
and T2 above are actually container managed transactions, each running in
response to REST API requests. They should be bound 1:1 with underlying
PostgreSQL transactions, but perhaps t
"Steve Dodd" writes:
> Say we have two transactions run sequentially: T1 writes some data, and T2
> reads the written data. There is a non-zero time delay between the apparent
> T1 commit, and the subsequent T2 query.
> Is there any guarantee that the data written in T1 will be visible to the
>
Say we have two transactions run sequentially: T1 writes some data, and T2
reads the written data. There is a non-zero time delay between the apparent T1
commit, and the subsequent T2 query.
Is there any guarantee that the data written in T1 will be visible to the query
in T2?
We have a situ
