<[email protected]> 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). Dag
