Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 9 Apr 2012 16:27:20 +0000 (UTC)
From: "Rick Hillegas (Updated) (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <292344783.3176.1333988840950.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1925636408.2525.1333976359209.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-5687) Back out the concurrency improvements
 for identity columns introduced by derby-4437
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas updated DERBY-5687:
---------------------------------

    Attachment: derby-5687-03-aa-adjustUserDocs.diff

Attaching derby-5687-03-aa-adjustUserDocs.diff. This patch adjusts the reference guide so that it no longer mentions identity columns when discussing sequence pre-allocators. Committed at subversion revision 1311312.

Touches the following files:

M       src/ref/rrefsqlj37836.dita
M       src/ref/rrefsqljcreatesequence.dita
M       src/ref/rrefproperpreallocator.dita

                
> Back out the concurrency improvements for identity columns introduced by derby-4437
> -----------------------------------------------------------------------------------
>
>                 Key: DERBY-5687
>                 URL: https://issues.apache.org/jira/browse/DERBY-5687
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.9.0.0
>            Reporter: Rick Hillegas
>         Attachments: derby-5687-01-aa-backOutImprovement.diff, derby-5687-02-aa-publicAPI.diff, derby-5687-03-aa-adjustUserDocs.diff
>
>
> DERBY-4437 attempted to improve the concurrency of identity columns by using SYSSEQUENCE-style sequence generators. These improvements caused NsTest to behave differently than it used to and they disclosed a problem in clearing the identity cache. The community lost confidence in this solution and it was backed out of the 10.8 branch under issue DERBY-5448. This new issue is filed to back the improvements out of the 10.9 trunk. Further useful discussion about how to improve the concurrency and correctness of identity columns has been taking place on DERBY-5443 and DERBY-5493.
> For the 10.9 release, identity columns will return to their old behavior of being ill-suited for high concurrency applications. Applications which need higher concurrency should be re-coded to use sequences rather than identity columns.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira