Hi!
(Just to make clear: Legolas Woodland and I have a similar Problem with
remaining locks, but different environments...)
I had the remaining locking problem with Derby 10.0.2.1 on IBM (AIX).
After updating to Derby 10.1.1.0 I *could not* reproduce the effect again!
Additional info: for our
Hi
Thank you for such complete post.
I have the problem yet and i could not solve it until now.
It will be good is some one with more experience look at this problem
and provide some tips to solve this problem.
Thank you
Klas U. wrote:
Dear all,
I've got a similar Problem with Derby locks
some suggestions.
Do you have the ability to try it out with a more recent version of
Derby, say the latest 10.1 release?
In debugging this what I would do is set the property to output the
queries to the derby.log. The faq on debugging lock timeout's apply's
to your situation:
Dear all,
I've got a similar Problem with Derby locks like it was described in
Deby create LOCK on my table and do not release it , what is my
mistake ?.
I have an JDBC application that uses a Derby 10.0.2.1 Network Server
on an IBM AIX machine.
My application performs delete- and
Legolas Woodland wrote:
Hi
Thank you for reading my post.
I have an update statement which i execute over a table in my database.
now when i execute the update statement from my application (even after
i exit the method that update the table)
i can not use select statement over the same table.
Hi
Thank you for reading my post.
I have an update statement which i execute over a table in my database.
now when i execute the update statement from my application (even after
i exit the method that update the table)
i can not use select statement over the same table.
here is my update
