[Glass] transactionConflicts, commitResult is readOnly ?

Dale Henrichs via Glass glass at lists.gemtalksystems.com
Wed Mar 22 11:40:10 PDT 2017

On 03/22/2017 08:21 AM, Johan Brichau via Glass wrote:
> Mariano,
> Thanks for sharing that piece of code.
> It seems a bit different in my case.
> By tracing I noticed that it happens right after a seemingly succesful 
> commit. I.e. the following statements happen immediately one after the 
> other:
> System commitTransaction
>  —> returns true.
> System transactionConflicts
>  —> marks the readOnly ‘commitResult’
> Any subsequent commit will always return true but nothing is ever 
> committed.
> Puzzled…

It's puzzling to us as well ... can you provide us with a simple test 
case ... #readOnly should indicate that there were no persistent objects 
modified by the session doing the commit, and does not represent a 
status of the system, in fact a #readOnly commit should be the 
equivalent of an abort ...


More information about the Glass mailing list