Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 12613 invoked from network); 2 Dec 2009 23:06:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Dec 2009 23:06:44 -0000 Received: (qmail 10138 invoked by uid 500); 2 Dec 2009 23:06:43 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 10111 invoked by uid 500); 2 Dec 2009 23:06:43 -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 10083 invoked by uid 99); 2 Dec 2009 23:06:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Dec 2009 23:06:43 +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; Wed, 02 Dec 2009 23:06:40 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id CF93A234C48D for ; Wed, 2 Dec 2009 15:06:20 -0800 (PST) Message-ID: <1395506241.1259795180848.JavaMail.jira@brutus> Date: Wed, 2 Dec 2009 23:06:20 +0000 (UTC) From: "Martin D. (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-4452) Enhance docs to clarify handling of internal id counter for generated by default keys In-Reply-To: <2092637653.1258717779785.JavaMail.jira@brutus> 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-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785050#action_12785050 ] Martin D. commented on DERBY-4452: ---------------------------------- Hmm, it seems to me that the documentation was modified within the last two weeks. So sure, now everything should be clear ;) Thanks for your support. > Enhance docs to clarify handling of internal id counter for generated by default keys > ------------------------------------------------------------------------------------- > > Key: DERBY-4452 > URL: https://issues.apache.org/jira/browse/DERBY-4452 > Project: Derby > Issue Type: Improvement > Components: Documentation > Affects Versions: 10.5.3.0 > Environment: derby 10.5.3.0, jdbc, embedded db > Reporter: Martin D. > Priority: Minor > > it seem that the internal auto id counter for generating the keys (ids) is not updated when a value with a fix id is inserted. > sample code: > try { > Connection con = DriverManager.getConnection("jdbc:derby:db/data/tmp;create=true"); > Statement stmt = con.createStatement(); > stmt.executeUpdate( > "CREATE TABLE testtable (id INTEGER NOT NULL GENERATED BY DEFAULT AS IDENTITY, value INT NOT NULL, PRIMARY KEY(ID))"); > // insert a few test values with auto id > stmt.execute("INSERT INTO testtable (value) VALUES (1),(2),(3)"); > // insert more values with fix id > stmt.execute("INSERT INTO testtable (id,value) VALUES (4,4),(5,5),(6,6)"); > // try to insert more values with auto id > // -> will throw SQLIntegrityConstraintViolationException (SQLState 23505) > stmt.execute("INSERT INTO testtable (value) VALUES (7)"); > stmt.close(); > con.close(); > } catch (Exception e) { > e.printStackTrace(); > } -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.