Is 1.4 with MV_STORE=false as stable as 1.3 builds? Or is there anything more unstable about this build when MV_STORE is disabled?
Thanks, Gili On Friday, September 12, 2014 11:21:30 AM UTC-4, Noel Grandin wrote: > > You could use 1.4 with MV_STORE=false, then you'd get the 1.3 storage > engine. > > On 2014-09-12 04:17 PM, cowwoc wrote: > > Hi Noel, > > > > Can you release an updated version of 1.3? I don't think I can use 1.4 > beta in production. > > > > Thanks, > > Gili > > > > On 12/09/2014 3:49 AM, Noel Grandin wrote: > >> This has been fixed in a newer version of H2. > >> > >> On 2014-09-12 04:39 AM, Gili wrote: > >>> Hi, > >>> > >>> I am getting "Commit or rollback is not allowed within a trigger" > under H2 1.3.176 but I am not actually rolling > >>> anything back. As far as I understand the following sequence of events > occurs: > >>> > >>> 1. Java code invokes: delete from PARTICIPANT where > PARTICIPANT.LAST_SEEN_TIME < ? > >>> 2. A "after delete" trigger runs, invoking: delete from PERMISSION > where ID = ? (at CascadeToPermission.java:80) > >>> 3. This triggers a rollback (looking at the H2 source code, caused by > a deadlock) > >>> 4. H2 throws the following exception: > >>> > >> > > > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
