Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 25 Mar 2011 16:40:05 +0000 (UTC)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <76622605.11567.1301071205989.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <777536248.9593.1301001725734.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (DERBY-5151) Sequence without cache
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-5151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011272#comment-13011272 ] 

Rick Hillegas commented on DERBY-5151:
--------------------------------------

Aha. My dyslexic eyes now see Bryan's point that Oracle and DB2 differ in the treatment of the syntactic sugar: DB2 puts a space between the NO and the CACHE. For me, that argues for not supporting the syntactic sugar and just going with the Postgres syntax. What else am I missing? Thanks.

> Sequence without cache
> ----------------------
>
>                 Key: DERBY-5151
>                 URL: https://issues.apache.org/jira/browse/DERBY-5151
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Mark Holster
>         Attachments: sequence-no-cache.patch
>
>
> Currently, a sequence in Derby always uses a pre allocating cache. I'm working on an usecase which requires a number to increase with a fixed value. The usecase fails after a restart because of the pre allocating cache.
> I've created a patch that adds the options CACHE | NO CACHE to the create sequence statement. When no cache is provided, the pre allocating cache size will be set to 1, which results in a "no cache sequence".
> I've followed the CYCLE | NO CYCLE code as much as possible. Tested it in my own app and it seems to work fine.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira