[
https://issues.apache.org/jira/browse/DERBY-5151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011216#comment-13011216
]
Mark Holster commented on DERBY-5151:
-------------------------------------
Hi Bryan,
You are right, my proposed solution has a different syntax than the 4
mentioned. That is because it seems logical to me to follow the "cycle | no
cycle" options. Actually, I don't care how the syntax is. I was wondering if a
property really is desired when most vendors allow this by sql. I personally
find a property more inconvenient to maintain than non standardized sql. Is a
sequence standardized anyway??
But indeed, that's my opinion. And like I said, I'm fine with creating a patch
that has a property based solution. I was just wondering the sql bases solution
was considered.
Mark
> 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
