You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many database owners create their own custom concepts in the 2B+ range to represent some local values. We recently ran into an issue trying to use these concepts in ATLAS. Come to find out these concepts need to stay under 2,147,483,648 to be viable in the standard tools. It would be good to add a check for this.
The text was updated successfully, but these errors were encountered:
let's get this added (ghost of Clair past agrees - #248 😛 ). i think the best way to implement this will be the overhaul of cdmDatatype to truly check column types against the CDM specs. (this value and above won't be able to exist in a 4 byte integer col)
if we want to add a short term patch we could also require integer cols (the only ones checked right now in cdmDatatype anyways) to be <2147483648.
Many database owners create their own custom concepts in the 2B+ range to represent some local values. We recently ran into an issue trying to use these concepts in ATLAS. Come to find out these concepts need to stay under 2,147,483,648 to be viable in the standard tools. It would be good to add a check for this.
The text was updated successfully, but these errors were encountered: