fix(seed): handle finite FK generation feedback

[machado144]

Summary

• allow tables without primary keys to generate multiple rows without false uniqueness collisions
• deterministically enumerate finite FK primary-key combinations for identifying and many-to-many tables, then surface capped row counts as warnings
• preserve exact column DDL types and cap generated string values to declared char/varchar lengths
• map MySQL bit columns to boolean-safe generated values and cover the insert path in integration tests
• let strict temporal/boolean/json DB types override semantic name guesses, and map generic temporal names to date/time fakers
• add concise serve UI feedback for schema graph loading and clone-schema phases/progress

Generate values that fit the column type & constraints

• temporal primary-key columns get a real date/time/datetime instead of a sequential integer (a DATE in a composite PK was seeded as 1 → Incorrect date value)
• UNIQUE numeric/temporal columns get a collision-free monotonic sequence — the numeric analog of uuid. They previously got a uuid string a numeric column can't store (Data truncated), or a random number() that collides at high row counts (Duplicate entry)
• decimal/numeric generators are sized to the declared precision/scale: scale-0 columns get integers, and small-precision columns (e.g. decimal(3,2)) are bounded so values never exceed the column (Out of range value)
• README + docs/schema.md mapping rules updated to match

Serve UI

• stream per-table progress during the truncate phase, mirroring the insert phase (no more frozen "Truncating tables" on large schemas). MySQL truncates per table so progress is genuine; PostgreSQL clears atomically and reports completion

Tests (TDD: reproduced before fixing)

• failing-first unit tests in internal/faker for every mapping/PK path, plus money-type, precision-bounded decimal, and a 5000-row unique-sequence no-collision check
• generic regression tables in the integration schema (Postgres + MySQL): unique numeric + zero-scale/small-precision decimals, single-column and composite temporal primary keys; a 2000-row UNIQUE-numeric insert reproducing the duplicate-key failure; and per-table truncate-progress assertions
• DDL uses only universally-supported features, so the matrix (PG 13/15/17 × MySQL 5.7/8.0/8.4) all pass

Tests

• go test ./internal/... → 437 pass
• cd integration && go test -tags integration -count=1 ./... → pass on Postgres + MySQL
• go build ./...

[github-actions]

StructLint — All checks passed

168 rules validated against .structlint.yaml. No violations found.

_{View full run · Powered by StructLint}