Description
When inserting relationships to postgres tables in cohort diagnostics I get an error that the 'is_hierarchical' and 'defines_ancestry' columns overflow (note they are defined as varchar(1) here but they are defined as unbounded TEXT in the sqlite common data model ddl.
When checking in sqlite the values all appear to be '0.0' - this causes cohort diagnostics unit tests to fail because its taking the 0.0 values from sqlite and trying to insert them in to postgres:
https://github.com/OHDSI/CohortDiagnostics/actions/runs/10579576275/job/29312378749#step:8:5416
I think this is maybe a bug I have seen before being caused by the sqlite DBI driver creeping up in DatabaseConnector:
OHDSI/DatabaseConnector#280
Essentially the value is thrown in to a csv as a 0, then when it is loaded it is turned into a numeric. When the DBI sqlite driver sees a numeric it automatically adds the floating point precision. This value is then finding its way into the CohortDiagnostics export (which I can work around).
Description
When inserting relationships to postgres tables in cohort diagnostics I get an error that the 'is_hierarchical' and 'defines_ancestry' columns overflow (note they are defined as varchar(1) here but they are defined as unbounded
TEXTin the sqlite common data model ddl.When checking in sqlite the values all appear to be '0.0' - this causes cohort diagnostics unit tests to fail because its taking the 0.0 values from sqlite and trying to insert them in to postgres:
https://github.com/OHDSI/CohortDiagnostics/actions/runs/10579576275/job/29312378749#step:8:5416
I think this is maybe a bug I have seen before being caused by the sqlite DBI driver creeping up in DatabaseConnector:
OHDSI/DatabaseConnector#280
Essentially the value is thrown in to a csv as a 0, then when it is loaded it is turned into a numeric. When the DBI sqlite driver sees a numeric it automatically adds the floating point precision. This value is then finding its way into the CohortDiagnostics export (which I can work around).