Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Date: Thu, 1 Sep 2011 14:04:09 +0000 (UTC)
From: "Michael Dick (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Message-ID: <18906462.6769.1314885849842.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (OPENJPA-2045) NAME is a valid column name for H2
 databases.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

NAME is a valid column name for H2 databases.
---------------------------------------------

                 Key: OPENJPA-2045
                 URL: https://issues.apache.org/jira/browse/OPENJPA-2045
             Project: OpenJPA
          Issue Type: Bug
          Components: jdbc
    Affects Versions: 2.1.0, 2.2.0
            Reporter: Michael Dick
            Priority: Minor


This issue was originally reported on the users mailing list : http://openjpa.208410.n2.nabble.com/GenerationType-TABLE-question-column-name-suffixed-with-0-td6729676.html. 

The H2 DBDictionary is picking up the default list of invalid column names from openjpa-jdbc/src/main/resources/org/apache/openjpa/jdbc/sql/sql-keywords.rsrc, which includes "NAME". As a result we're trying to fix the column so that it contains a valid identifier, and end up with the wrong value. 

Users can work around the problem by delimiting columns in their annotations or xml mapping files, for example : 
@javax.persistence.TableGenerator(
    name = "fred", 
    table = "jpa_sequence", 
    pkColumnName = "\"name\"", 
    valueColumnName = "last_value", 
    pkColumnValue = "fred", 
    allocationSize = 500)

To fix the problem we need to either remove NAME from the default list, or manually remove it in the H2 Dictionary. Some additional investigation may be needed to determine whether this is a problem for other databases too. 


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira