[
https://issues.apache.org/jira/browse/CAY-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Huss closed CAY-1863.
--------------------------
Resolution: Fixed
Fix Version/s: 3.2.M2
> 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
> Fix For: 3.2.M2
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)
