You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "John Huss (JIRA)" <ji...@apache.org> on 2013/08/16 22:57:50 UTC

[jira] [Created] (CAY-1863) Make determining whether a particular database type supports length adapter-specific not universal

John Huss created CAY-1863:
------------------------------

             Summary: Make determining whether a particular database type supports length adapter-specific not universal
                 Key: CAY-1863
                 URL: https://issues.apache.org/jira/browse/CAY-1863
             Project: Cayenne
          Issue Type: Bug
          Components: Core Library
    Affects Versions: 3.2M1
            Reporter: John Huss
            Assignee: John Huss
            Priority: Minor


Database implementations vary in regard to which data types they allow a length to be specified for.  So the static method TypesMapping.supportsLength should be deprecated and replaced by an adapter-specific method that can be tweaked for each supported database.

The current implementation causes some bugs in particular with the MergerFactory which relies on the global method TypesMapping.supportsLength when adding a new column to an existing table or changing the datatype of an existing column.  The specified length may wrongly be ignored in this case.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira