d1 import: broaden strftime() date/time coverage, fix boolean CHECK literals

[claude]

Requested by Elom Gomez · Slack thread

Summary

D1 imports could generate invalid Postgres DDL in two cases:

• A timestamp-like TEXT column was converted to TIMESTAMPTZ, but its SQLite strftime(...) default was copied as a string literal.
• An INTEGER column was converted to BOOLEAN, but its CHECK constraint still compared it with 0 and 1.

This PR translates both patterns into valid Postgres expressions while leaving unrelated columns and defaults alone.

What changed

Date and time defaults

The importer now recognizes common D1 strftime(...) defaults that use current-time values, ISO-8601 or date formats, Unix timestamps, and supported date modifiers.

For example:

DEFAULT (strftime('%Y-%m-%dT%H:%M:%SZ', 'now'))

becomes:

DEFAULT date_trunc('second', now())

Only mappings with a known Postgres equivalent are converted. Unsupported typed defaults are omitted instead of producing invalid DDL; TEXT defaults keep the existing literal fallback.

Boolean CHECK constraints

When an SQLite INTEGER column is inferred as a Postgres BOOLEAN, standalone 0 and 1 literals in direct comparisons, IN, and BETWEEN expressions are converted to false and true.

For example:

CHECK (is_active IN (0, 1))

becomes:

CHECK (is_active IN (false, true))

The rewrite applies only to columns already selected for boolean coercion. Decimal, exponent, hexadecimal, signed, and arithmetic expressions are left intact rather than partially rewritten.

Testing

• go test ./internal/import/d1/...
• go vet ./internal/import/d1/...
• GitHub build, lint, license, and Bugbot checks

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 3 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 2d71548. Configure here.}