While validating a CSV file using Tablesaw version 0.43.1, I encountered a type casting issue: columns intended as DateColumn were automatically detected as StringColumn. This led to downstream type mismatch errors during validation. The source CSV contains date values in standard ISO format, and the schema was defined to expect DateColumn. Requesting guidance on whether this is a parsing limitation, a configuration oversight, or a bug in the column inference logic.