cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Huss (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAY-1863) Make determining whether a particular database type supports length adapter-specific not universal
Date Fri, 16 Aug 2013 20:59:48 GMT

     [ https://issues.apache.org/jira/browse/CAY-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

John Huss updated CAY-1863:
---------------------------

    Attachment: 0001-CAY-1863-Make-determining-whether-a-particular-datab.patch
    
> 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
>         Attachments: 0001-CAY-1863-Make-determining-whether-a-particular-datab.patch
>
>
> 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

Mime
View raw message