Closed GoogleCodeExporter closed 9 years ago
This error does not occur in 1.2.126, if the database is created from scratch.
If we
create the database with 1.1.118, then update to 1.2.126, the error still shows.
Original comment by dmoeb...@gmx.net
on 14 Jan 2010 at 10:38
This error also occurs in 1.2.126 when using MVCC=TRUE;PAGE_STORE=FALSE with a
newly
created database.
Original comment by dmoeb...@gmx.net
on 14 Jan 2010 at 12:13
I will try to fix it (I didn't have time yet to reproduce it).
It's strange that it's not reproducible without the page store.
Original comment by thomas.t...@gmail.com
on 15 Jan 2010 at 8:19
Hi,
I found the problem, it is fixed in the trunk.
Regards,
Thomas
Original comment by thomas.t...@gmail.com
on 23 Jan 2010 at 6:20
Great! Thanks a lot.
To backport this fix to 1.1.118, I guess I have to add this line
row.setVersion(row.getVersion() - 1);
to UndoLogRecord.java somewhere. I'll try this for myself. It doesn't seem hard
to do.
Btw.: I think your new testcase TestTransaction.testRollback() is missing a
rollback() in the second part, where you delete from master:
try {
stat.execute("delete from master");
fail();
} catch (SQLException ex) {
// ok
rollback(); // <-- this one is missing here
}
Otherwise you'll don't test the original error.
Original comment by dmoeb...@gmx.net
on 25 Jan 2010 at 9:07
Sorry, Thomas, this bug is not yet fixed. :-(
If you change your testcase TestTransaction.testRollback() so that it inserts 3
rows
instead of 2, you'll see that you don't get the expected result. I attached a
patch
file to show you how I modified your testcase.
Note that I added conn.rollback() in the catch clause, but this is not
required: the
bug shows up with or without rollback.
Original comment by dmoeb...@gmx.net
on 29 Jan 2010 at 4:54
Attachments:
I tried to work around the problem, but I'm afraid I will not be able to fix
this
problem, I'm sorry. When using MVCC, it looks like the page store is the only
possible solution.
Original comment by thomas.t...@gmail.com
on 30 Jan 2010 at 11:01
Could you please elaborate on this? What's the difference between page store
and old
file store so that the problem is solved in the first case and cannot be solved
in
the latter case?
Original comment by dmoeb...@gmx.net
on 1 Feb 2010 at 8:33
> Could you please elaborate on this?
I'm sorry it's a bit complicated. I would have to explain a lot; I'm afraid I
don't
have the time to do that.
Original comment by thomas.t...@gmail.com
on 6 Feb 2010 at 4:53
I'm afraid I will not be able to fix it with version 1.1.x (page store
disabled). I
think it doesn't make sense to keep the issue open because it works with the
current
release (page store enabled).
Original comment by thomas.t...@gmail.com
on 20 Feb 2010 at 9:49
Original issue reported on code.google.com by
dmoeb...@gmx.net
on 14 Jan 2010 at 10:21Attachments: