[Feature] Have ASAPPlanner support Date32 and Date64 types in DataFusion

[Selvomega]

Found the following error when testing ASAP-Planner
skipping "U-P3l" — lowering failed: unsupported feature: Arrow type: Date32

Suggestion: extend arrow_to_dtype in ASAPPlanner/crates/frontend-sql/src/sql/types.rs
However, I do not know if we should

• Add Date32/Date64 as an extra internal type, or
• convert them to Timestamp

[zzylol]

My understanding is, for example SELECT CAST('2026-09-14' AS DATE), DataFusion identifies the result as Date32. ASAPPlanner doesn’t recognize that type and reports an unsupported feature: Arrow type: Date32.

Date32 and Date64 both represent calendar dates; they use different storage formats. There are three ways to support them:

• Use existing Timestamp, treating a date as midnight on that date; small change, but loses the distinction between a date and a timestamp
• Add Date32 and Date64, preserving the type DataFusion provides; adds two types, but avoids conversion assumptions.

I recommend adding Date32 and Date64 initially. And simply recognizing the type names isn’t enough: date columns, date literals, and CAST(... AS DATE) must all work correctly for the fix to be complete.

[Selvomega]

FYI: Adding Date32 and Date64 will make the type narrow waist dirtier.
(check arrow_to_dtype in ASAPPlanner/crates/frontend-sql/src/sql/types.rs)
Are you sure that it is ok to do so?

[zzylol]

Yes, "narrow waist" comes from post-ASAP IR.