Open GoogleCodeExporter opened 8 years ago
This is not related to the MV_STORE. It also fails when you don't enable it.
When using FOR UPDATE, the database tries to convert the query to a UPDATE
statement, but that's not so easy when using a join.
As a workaround, what you could do is write an UPDATE statement yourself, one
that does a dummy update, for example SET X=X.
Original comment by thomas.t...@gmail.com
on 21 Jan 2014 at 8:38
I'm a little confused by the last comment. This functionality works in 1.3.176
but fails in 1.4.178.
1. What feature does not support FOR UPDATE and JOIN? Is it MVCC or MV_STORE?
2. Why is it harder to convert a query an UPDATE statement when one of these
features is enabled?
Original comment by cow...@bbs.darktech.org
on 5 May 2014 at 3:10
Thomas? Can you please answer the aforementioned questions?
Original comment by cow...@bbs.darktech.org
on 21 Jun 2014 at 6:31
[deleted comment]
Any progress on this topic?
We switched to the nightly build lately because of the deadlock issues in the
stable version. We found a discussion
http://h2-database.66688.n3.nabble.com/Deadlock-trying-to-lock-a-table-that-is-a
lready-locked-td4030281.html that exactly described our deadlock problem and
the nightly build fixed that issue. But now we have this "feature not
supported" issue instead.
Original comment by gsmits...@gmail.com
on 18 Nov 2014 at 7:34
We don't support the combination of
(1) MVCC=true
(2) FOR UPDATE
(3) GROUP/DISTINCT/AGGREGATE/JOIN
Original comment by noelgrandin
on 6 Jan 2015 at 7:34
Original issue reported on code.google.com by
g...@maginatics.com
on 21 Jan 2014 at 12:03