Skip to content

Conversation

@cpsievert
Copy link
Contributor

Summary

  • Fixed DataFrameSource.get_schema mapping nw.Datetime to "TIME" instead of "TIMESTAMP"
  • Updated range check to include TIMESTAMP so datetime columns continue to show range info

Details

A datetime (date + time) should be represented as TIMESTAMP, not TIME (which is for time-only values). This affects the schema information provided to the LLM for query generation.

Test plan

  • Existing tests pass (pytest pkg-py/tests/test_datasource.py)
  • Manual verification that datetime columns now show as TIMESTAMP in schema output

🤖 Generated with Claude Code

DataFrameSource.get_schema was mapping nw.Datetime to "TIME" instead of
"TIMESTAMP". A datetime (date + time) should be represented as TIMESTAMP,
not TIME (which is for time-only values).

Also updated the range check to include TIMESTAMP instead of TIME so that
datetime columns continue to show range information in the schema.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@cpsievert cpsievert marked this pull request as draft January 14, 2026 16:46
Adds a test that verifies datetime columns in DataFrameSource are
correctly mapped to TIMESTAMP (not TIME) in the schema output.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants