Return-Path: 
 <dev-return-16480-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org>
Delivered-To: apmail-openjpa-dev-archive@www.apache.org
Received: (qmail 39860 invoked from network); 17 May 2010 18:11:04 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 17 May 2010 18:11:04 -0000
Received: (qmail 51135 invoked by uid 500); 17 May 2010 18:11:03 -0000
Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org
Received: (qmail 51101 invoked by uid 500); 17 May 2010 18:11:03 -0000
Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@openjpa.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@openjpa.apache.org>
List-Post: <mailto:dev@openjpa.apache.org>
List-Id: <dev.openjpa.apache.org>
Reply-To: dev@openjpa.apache.org
Delivered-To: mailing list dev@openjpa.apache.org
Received: (qmail 51069 invoked by uid 99); 17 May 2010 18:11:03 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 May 2010 18:11:03 +0000
X-ASF-Spam-Status: No, hits=-1435.3 required=10.0
	tests=ALL_TRUSTED,AWL
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; Mon, 17 May 2010 18:11:02 +0000
Received: from thor (localhost [127.0.0.1])
	by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o4HIAgtD026196
	for <dev@openjpa.apache.org>; Mon, 17 May 2010 18:10:42 GMT
Message-ID: <8604341.88091274119842183.JavaMail.jira@thor>
Date: Mon, 17 May 2010 14:10:42 -0400 (EDT)
From: "Heath Thomann (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Created: (OPENJPA-1668) User's ''DBDictionary.sequenceSQL'
 setting not being honored on zOS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394

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: 2.0.0, 1.2.2, 1.0.3
            Reporter: Heath Thomann
            Assignee: Heath Thomann
            Priority: Minor


When setting/overriding the 'DBDictionary.sequenceSQL' value via a property in the persistence.xml file, as follows:

	<property name="openjpa.jdbc.DBDictionary" value="db2(sequenceSQL='SELECT SCHEMA AS SEQUENCE_SCHEMA, NAME AS SEQUENCE_NAME FROM CIDB2.SYSSEQUENCES')"/>                                                        

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.