db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dag.wan...@oracle.com (Dag H. Wanvik)
Subject Re: funny behavior
Date Thu, 07 Apr 2011 22:10:49 GMT
<Malte.Kempff@de.equens.com> writes:

> 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?

Reads also set locks to implement the transactional guarantees of SQL
(read locks), so this is normal (unless you use READ UNCOMMITTED mode).


View raw message