openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laird Nelson (JIRA)" <j...@apache.org>
Subject [jira] Created: (OPENJPA-1514) DBDictionary instances do not call setAutoAssigned() where appropriate
Date Tue, 16 Feb 2010 13:41:28 GMT
DBDictionary instances do not call setAutoAssigned() where appropriate
----------------------------------------------------------------------

                 Key: OPENJPA-1514
                 URL: https://issues.apache.org/jira/browse/OPENJPA-1514
             Project: OpenJPA
          Issue Type: Bug
          Components: sql
    Affects Versions: 2.0.0-beta, 2.0.0-M3, 2.0.0-M2, 2.0.0-M1, 1.2.2, 1.2.1, 1.2.0, 1.1.0,
1.0.3, 1.0.2, 1.0.1, 1.0.0, 1.0.4, 1.0.5, 1.1.1, 1.2.3, 1.3.0, 2.0.0, 2.0.1, 2.1.0
            Reporter: Laird Nelson


Although a DBDictionary instance by definition has access to the database's information that
would allow it to mark a new Column as being autoassigned, DBDictionaries do not do this in
their newColumn() method.  It seems to me that all DBDictinonary instances should be required
by contract to detect when a column is a database-managed identity or sequential column and
should call Column#setAutoAssigned(boolean) as appropriate.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message