Colin Rosenthal wrote:
On Tue, 2005-10-25 at 13:30, Knut Anders Hatlen wrote:
Colin Rosenthal <[EMAIL PROTECTED]> writes:
Hi all,
We have an application which uses derby in auto-commit=false mode.
For some reason a row in one of our tables cannot be updated from
our system. Attempting to do
On Tue, 2005-10-25 at 13:30, Knut Anders Hatlen wrote:
> Colin Rosenthal <[EMAIL PROTECTED]> writes:
>
> > Hi all,
> > We have an application which uses derby in auto-commit=false mode.
> > For some reason a row in one of our tables cannot be updated from
> > our system. Attempting to do so consis
Colin Rosenthal <[EMAIL PROTECTED]> writes:
> Hi all,
> We have an application which uses derby in auto-commit=false mode.
> For some reason a row in one of our tables cannot be updated from
> our system. Attempting to do so consistently produces a 40XL1 lock
> timeout error. I have shut down the
Hi all,
We have an application which uses derby in auto-commit=false mode.
For some reason a row in one of our tables cannot be updated from
our system. Attempting to do so consistently produces a 40XL1 lock
timeout error. I have shut down the system and gone in with ij and
updated this row "by han