Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 75682 invoked from network); 28 Jul 2008 21:27:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Jul 2008 21:27:23 -0000 Received: (qmail 36246 invoked by uid 500); 28 Jul 2008 21:27:22 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 36215 invoked by uid 500); 28 Jul 2008 21:27:22 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 36166 invoked by uid 99); 28 Jul 2008 21:27:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jul 2008 14:27:22 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED 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 Jul 2008 21:26:36 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4EDE8234C183 for ; Mon, 28 Jul 2008 14:26:32 -0700 (PDT) Message-ID: <204018556.1217280392321.JavaMail.jira@brutus> Date: Mon, 28 Jul 2008 14:26:32 -0700 (PDT) From: "Michael Dick (JIRA)" To: dev@openjpa.apache.org Subject: [jira] Closed: (OPENJPA-669) NativeSequences can be incremented within the business transaction In-Reply-To: <1642246732.1217279551691.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/OPENJPA-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dick closed OPENJPA-669. -------------------------------- Resolution: Fixed > NativeSequences can be incremented within the business transaction > ------------------------------------------------------------------ > > Key: OPENJPA-669 > URL: https://issues.apache.org/jira/browse/OPENJPA-669 > Project: OpenJPA > Issue Type: Bug > Affects Versions: 0.9.6, 0.9.7, 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.1.0 > Reporter: Michael Dick > Assignee: Michael Dick > Fix For: 1.2.0 > > > SQL Sequences are independent of the transaction. Therefore the same connection which is used to insert a row can be used to increment the sequence value. > Currently we treat these native sequences in the same manner as updating a sequence table - ie the work will be done on connection2 (aka the non-jta-data-source). This appears to be unnecessary and requires an additional datasource when running in a managed environment which can't suspend the current transaction > To resolve the problem I added a nativeSequenceType attribute to the DBDictionary class. This setting will be used to determine the whether the databases sequences are transactional, contiguous or non transactional (Default is contiguous). If the native sequences are transactional or contiguous they will be executed within the current transaction and will not require a second connection factory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.