I encountered problems when running DBMonster.
I configured DBMonster to use the following drivers:
org.gjt.mm.mysql.Driver
The connection is okay but when starting the 'feeding'-process it cancels with the following exception:
FATAL Runner - java.sql.SQLException Can't call commit when autocommit=true
I have tried several options to disable autocommit for MySQL but nothing helped (I am not sure whether it is even possible to disable it for normal myisam-type!?)
Do you know this problem? Did I forget something?
Fast help would really be appreciated!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've tested it and this is indeed a bug. I do not use MySQL so I didn't know that commit while autocommit is enabled could lead to error on that database. The solution is easy but recompilation of one class is needed.
In class pl.kernelpanic.dbmonster.connection.Transaction in method commit() line conn.commit() should be commented out. I'll do make more complex solution to this issue but first I must look closer on how this change will influence other RDBMSs.
Thanks for this bug report. If you want I can send recompiled version of DBMonster suitable for MySQL via email. Just tell me the address.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I encountered problems when running DBMonster.
I configured DBMonster to use the following drivers:
org.gjt.mm.mysql.Driver
The connection is okay but when starting the 'feeding'-process it cancels with the following exception:
FATAL Runner - java.sql.SQLException Can't call commit when autocommit=true
I have tried several options to disable autocommit for MySQL but nothing helped (I am not sure whether it is even possible to disable it for normal myisam-type!?)
Do you know this problem? Did I forget something?
Fast help would really be appreciated!
I've tested it and this is indeed a bug. I do not use MySQL so I didn't know that commit while autocommit is enabled could lead to error on that database. The solution is easy but recompilation of one class is needed.
In class pl.kernelpanic.dbmonster.connection.Transaction in method commit() line conn.commit() should be commented out. I'll do make more complex solution to this issue but first I must look closer on how this change will influence other RDBMSs.
Thanks for this bug report. If you want I can send recompiled version of DBMonster suitable for MySQL via email. Just tell me the address.
New version of dbMonster is out (1.0-beta3), which fixes the problem.
Thanks for your fast reply and bug-fix!
I'll try it out and stay tuned to this helpful tool.
gtx