Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 52647 invoked from network); 28 Dec 2009 10:22:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Dec 2009 10:22:56 -0000 Received: (qmail 64168 invoked by uid 500); 28 Dec 2009 10:22:56 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 64102 invoked by uid 500); 28 Dec 2009 10:22:56 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 64094 invoked by uid 99); 28 Dec 2009 10:22:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Dec 2009 10:22:56 +0000 X-ASF-Spam-Status: No, hits=-10.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Dec 2009 10:22:49 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 6AF06234C045 for ; Mon, 28 Dec 2009 02:22:29 -0800 (PST) Message-ID: <1777304648.1261995749425.JavaMail.jira@brutus.apache.org> Date: Mon, 28 Dec 2009 10:22:29 +0000 (UTC) From: "Knut Anders Hatlen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-712) Support for sequences In-Reply-To: <665694319.1132200569950.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794794#action_12794794 ] Knut Anders Hatlen commented on DERBY-712: ------------------------------------------ Looks like NextSequenceNode.java was forgotten in the previous commit. Added that file and committed revision 894146. > Support for sequences > --------------------- > > Key: DERBY-712 > URL: https://issues.apache.org/jira/browse/DERBY-712 > Project: Derby > Issue Type: Improvement > Components: SQL > Environment: feature request > Reporter: Tony Dahbura > Assignee: Suran Jayathilaka > Fix For: 10.6.0.0 > > Attachments: altertable.diff, catalogs_a.patch, catalogs_b.patch, catalogs_c.patch, catalogs_d.patch, catalogs_e.patch, catalogs_f.patch, catalogs_f_2.patch, catalogs_g.diff, catalogs_h.diff, create_drop_sequence_a.patch, create_drop_sequence_b.patch, create_drop_sequence_c.patch, create_drop_sequence_d.patch, create_sequence_a.patch, derby-712-02-aa-privilegeNodeCleanup.diff, SequenceGenerator.html, sequences_next_value_a.patch > > > Would like to see support added for sequences. This would permit a select against the sequence to always obtain a ever increasing/decreasing value. The identity column works fine but there are times for applications where the application needs to obtain the sequence number and use it prior to the database write. Subsequent calls to the table/column would result in a new number on each call. > SQL such as the following: > SELECT NEXT VALUE FOR sequence_name FROM sometable ; would result in a next value. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.