· 7 min read
Your Dates Are 543 Years Off, and Every Row Loaded Successfully
A calendar convention read as the wrong system shifts every date by a fixed offset that can be centuries, and nothing rejects the result because the output is a valid date. The same class covers text moving through a legacy code page, numeric separators, and time zones stored without one. These failures pass row counts, null checks and schema validation, which is why a migration has to test for them explicitly rather than wait for them.