Turning off MVCC is not feasible at this time. And we are not uncomfortable with MVCC.
It's only that we are not aware of MVCC's limitations (like concurrent updates when a select max() is run). We worked around the issue by denormalizing the data and maintaining that MAX value on a separate table. Thanks for all the feedback. On Tuesday, October 2, 2012 8:45:24 AM UTC+2, Noel Grandin wrote: > > Turn off MVCC. > > Thomas, perhaps the MVCC option should be disabled, since it keeps > causing problems ? > > On 2012-10-01 10:02, Ignasi Marimon-Clos i Sunyol wrote: > > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/8hun37BRkogJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
