Alright, that is unfortunately. We will have to stick to *1.4.197*. And it's not possible to override the behaviour using compability modes? For example *MODE=MYSQL*
Yes, we need to lock all entries containing the `report_id` inorder to ensure the number serie. Example table report_id, sequence 1, 1 1, 2 1, 3 1, 4 2, 1 2, 2 Thanks for the reply. Regards Nicklas On Friday, May 3, 2019 at 2:40:33 PM UTC+2, Evgenij Ryazanov wrote: > > Hello. > > SELECT_FOR_UPDATE_MVCC was useless after other changes in H2. > > The exception that you got describes the situation pretty clear: you can't > use FOR UPDATE clause when you use aggregates (or distinct). Grouped > queries don't return the original rows, FOR UPDATE is disallowed in such > queries by many databases. You need to perform a regular query that selects > and returns all rows that you want to lock. > > https://h2database.com/html/commands.html#select > > BTW, do you really need to lock all rows with specific report_id? > -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
