From dev-return-17113-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Thu Aug 12 22:09:38 2010 Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 20037 invoked from network); 12 Aug 2010 22:09:38 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 12 Aug 2010 22:09:38 -0000 Received: (qmail 34653 invoked by uid 500); 12 Aug 2010 22:09:38 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 34514 invoked by uid 500); 12 Aug 2010 22:09:37 -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 34501 invoked by uid 99); 12 Aug 2010 22:09:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Aug 2010 22:09:37 +0000 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.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Aug 2010 22:09:37 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o7CM9FkT002806 for ; Thu, 12 Aug 2010 22:09:17 GMT Message-ID: <582334.315311281650955913.JavaMail.jira@thor> Date: Thu, 12 Aug 2010 18:09:15 -0400 (EDT) From: "Michael Dick (JIRA)" To: dev@openjpa.apache.org Subject: [jira] Resolved: (OPENJPA-1668) User's ''DBDictionary.sequenceSQL' setting not being honored on zOS In-Reply-To: <8604341.88091274119842183.JavaMail.jira@thor> 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/OPENJPA-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dick resolved OPENJPA-1668. ----------------------------------- Fix Version/s: 1.3.0 2.0.1 Resolution: Fixed > User's ''DBDictionary.sequenceSQL' setting not being honored on zOS > -------------------------------------------------------------------- > > Key: OPENJPA-1668 > URL: https://issues.apache.org/jira/browse/OPENJPA-1668 > Project: OpenJPA > Issue Type: Bug > Affects Versions: 1.0.3, 1.2.2, 2.0.0 > Reporter: Heath Thomann > Assignee: Heath Thomann > Priority: Minor > Fix For: 1.2.3, 1.3.0, 2.0.1, 2.1.0 > > Attachments: OPENJPA-1668-1.2.x.patch.txt > > > When setting/overriding the 'DBDictionary.sequenceSQL' value via a property in the persistence.xml file, as follows: > > this value is not used when running DB2 on zOS. Rather, the 'default for zOS' is used, i.e.: "SELECT SCHEMA AS SEQUENCE_SCHEMA, NAME AS SEQUENCE_NAME FROM SYSIBM.SYSSEQUENCES";. > To understand how this is happening, let me describe how 'sequenceSQL' is defined/set at runtime. First, the ctor of DB2Dictionary is called, and the variable is set to a default: > sequenceSQL = "SELECT SEQSCHEMA AS SEQUENCE_SCHEMA, " > + "SEQNAME AS SEQUENCE_NAME FROM SYSCAT.SEQUENCES"; > After the DB2Dictionary ctor is called, openJPA assigns to 'sequenceSQL' the value defined in the system property. So at this point things are all good and the variable is set to what is defined in the prop. Where things go awry is when the method DB2Dictionary.connectedConfiguration is called. In the method there is some platform specific code which is executed which overwrites the sequenceSQL value: > // platform specific settings > switch (db2ServerType) { > case db2ZOSV8xOrLater: > ........ > sequenceSQL = "SELECT SCHEMA AS SEQUENCE_SCHEMA, " > + "NAME AS SEQUENCE_NAME FROM SYSIBM.SYSSEQUENCES"; > Thanks, > Heath -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.