Re: jdbc prepared statement (insert) apache derby
- From: Dyreatnews@xxxxxxx
- Date: Mon, 11 Sep 2006 10:10:26 +0200
"3rdshiftcoder" <go@xxxxxxxx> writes:
hi-
i put a unique index on a derby table.
it causes an sql error to be thrown .
A lock could not be obtained within the time requested
the gui acts unresponsive like it is trying...trying...trying
and then gives up and becomes repsonsive again.
i dont understand why my code hangs here.
i am using a prepared statement with an
insert statement and executeUpdate().
any reason or hints why this is happening would be really cool.
what i am (trying) to do is hook my jface swt listviewer
control to the db. i try to trap the error and make it so
if the value in the listviewer is already present, do not
add it to the listviewer a second time because of the unique index.
If you have the time, it would be really good of you could report this
problem to derby-user@xxxxxxxxxxxxx
Not many derby people follow this newsgroup, I'm afraid.
What you describe sounds like a bug, but it is hard to say without
seeing actual code and stack traces.
--
dt
.
- References:
- jdbc prepared statement (insert) apache derby
- From: 3rdshiftcoder
- jdbc prepared statement (insert) apache derby
- Prev by Date: Re: flawed transaction isolation level
- Next by Date: Re: java.sql.SQLRuntimeException: Cannot store DataSet instance to WeakHashMap
- Previous by thread: Re: jdbc prepared statement (insert) apache derby: SOLVED IGNORE
- Next by thread: java.sql.SQLRuntimeException: Cannot store DataSet instance to WeakHashMap
- Index(es):