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

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.2.M1
• Fix Version/s: 4.0.M2
• Component/s: Core Library
• Assignee: John Huss
• Reporter: John Huss
• Due: 16/Aug/13
• Created: 16/Aug/13 20:57
• Updated: 07/Aug/14 20:22
• Resolved: 07/Aug/14 20:22

Description

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.