Description of problem: The DDL creates cms_user_home_folder_map.section_id as a NUMERIC data type because of the property: BigDecimal sectionID = cms_user_home_folder_map.section_id; Because no type is defined the BigDeciamlAd adapter resolves the type to NUMERIC. The join on cms_user_home_folder_map.section_id however references content_sections.section_id which gets resolved to the INTEGER data type. SQL Server does not like to mix data types when referencing foreign keys. I could just create a SQL Server specific PDL for this but I also don't think it's a good idea to reference different data types together. Maybe in Oracle and Postgresql NUMERIC and INTEGER are the same data type or NUMERIC is smaller than INTEGER. But in Sql Server NUMERIC is defined as -10^38 +1 through 10^38 â1 and INTEGER is defined as 2^31 (-2,147,483,648) through 2^31 - 1 (2,147,483,647). If the same is true for Oracle and Postgresql then you have a larger value trying to match up with a smaller value which in very rare cases (id > 10^38 â1) can result in you not being able to create the relationship.
Sorry, I got that backwards. Since the primary key is an INTEGER it's ok to join them this way. You can always create the relationship. But I still don't think it's a good idea (:
Closing old tickets