Rick Hillegas created DERBY-7002:
------------------------------------

             Summary: Change the text of X0Y84 to advise users to tune the 
value of derby.language.sequence.preallocator
                 Key: DERBY-7002
                 URL: https://issues.apache.org/jira/browse/DERBY-7002
             Project: Derby
          Issue Type: Improvement
          Components: SQL
    Affects Versions: 10.15.0.0
            Reporter: Rick Hillegas


This is the LANG_TOO_MUCH_CONTENTION_ON_SEQUENCE error message. Right now it 
says the following:

{noformat}
Too much contention on sequence {0}. This is probably caused by an uncommitted
scan of the SYS.SYSSEQUENCES catalog. Do not query this catalog directly. 
Instead, use the SYSCS_UTIL.SYSCS_PEEK_AT_SEQUENCE function to view
the current value of a sequence generator.
{noformat}

Issue DERBY-6999 suggests that it would be good if the error message suggested 
another cause for the "too much contention" exception: The value of 
derby.language.sequence.preallocator may be too low. The error message should 
suggest that the user tune this value.

While we're at it, it might be good if the error messages noted the current 
friction with Statement.getGeneratedKeys() (see DERBY-6934). Currently, there 
is no workaround for that friction. Application code should not call that 
method.




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to