db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <knut.hat...@oracle.com>
Subject Re: Draft Release Notes for 10.8.3
Date Fri, 26 Oct 2012 08:41:28 GMT
Dag Wanvik <dag.wanvik@oracle.com> writes:

> On 25.10.2012 01:13, Katherine Marsden wrote:
>
>     Note for DERBY-5564: The SQL state of the error returned from a
>     lock timeout when the property "derby.locks.deadlockTrace=true" is
>     set will return 40XL1 rather than 40XL2. 40XL1 is the documented
>     SQL state for lock timeouts returned from Derby. 
>
> Good to warn that this has changed, but reading it again, do we had a
> policy of documenting the exact SQL states? If we now do, when did
> that change? (I believe we didn't in the past.)

The 10.0 reference manual had a list of common SQL states:
http://db.apache.org/derby/docs/10.0/manuals/reference/sqlj171.html

The list doesn't include lock timeout (40XL1), but that state was
mentioned other places in the reference manual:
http://db.apache.org/derby/docs/10.0/manuals/tuning/perf82.html

And in the developer's guide:
http://db.apache.org/derby/docs/10.0/manuals/develop/develop75.html

The latter also documents the now removed 40XL2 state.

In fact, the developer's guide still documents the 40XL2 state here:
http://db.apache.org/derby/docs/dev/devguide/cdevconcepts32861.html

I'll file a bug report to get that cleaned up.


-- 
Knut Anders

Mime
View raw message