Hi to all, I am using derby as embedded DataBase using just one simple table.
Several update and delete statements are defined though, in a certan way I use my program it is just executing a select statement. But now there is the funny thing: derby puts out 25001 error. Obviously it wants a commit for this select statement... is it because I also defined those other prepared statements or does derby want a commit generally even though it is just a select? There is also another Question. Looking at the log file I get from derby seeing the particular property to true, I see several commits in the beginning, that are not explicitly called by my own programm. Is this normal? Here the log extract: ---------------------------------------------------------------- 2011-04-07 15:48:39.666 GMT: Booten von Derby Version The Apache Software Foundation - Apache Derby - 10.5.1.1 - (764942): Instanz a816c00e-012f-30a6-aa04-000000146120 für das Datenbankverzeichnis C:\Dokumente und Einstellungen\z300057\workspace\SaaMixer\DB Das Ladeprogramm für Datenbankklassen wurde gestartet - derby.database.classpath='' 2011-04-07 15:48:39.884 GMT Thread[main,5,main] (XID = 28149), (SESSIONID = 0), (DATABASE = DB), (DRDAID = null), Committing 2011-04-07 15:48:39.884 GMT Thread[main,5,main] (XID = 28149), (SESSIONID = 0), (DATABASE = DB), (DRDAID = null), Rolling back 2011-04-07 15:48:39.884 GMT Thread[main,5,main] (XID = 28150), (SESSIONID = 1), (DATABASE = DB), (DRDAID = null), Committing 2011-04-07 15:48:39.884 GMT Thread[main,5,main] (XID = 28150), (SESSIONID = 1), (DATABASE = DB), (DRDAID = null), Committing ... Could somebody tell me why this happens and why there seem to be 2 sessions used? Thanks for hints in advance Malte
