Generated database types

src/lib/types/database.ts describes the database shape used by typed clients. It helps catch structural incompatibility; it does not authorize access or validate financial meaning.

When the schema changes

1. Apply the approved forward migration to the authorized target.
2. Verify the table or RPC’s actual runtime shape and permissions.
3. Update generated types from that shape.
4. Update service callers and API response contracts together.
5. Run the affected types and behavior checks.

Do not make a type change stand in for a database migration.

Database types versus API types

A database row can contain server-only or unrelated fields. A financial response should expose owned data with the currency, date and evidence needed by its consumer. Do not send an entire row simply because its generated type is easy to import.

RPC contracts

Read the actual function signature and return shape before changing a caller. Optional fields and financial precision affect domain behavior; satisfying TypeScript is not sufficient evidence of a correct command.

Common mistake

A cast can silence a mismatch while leaving the deployed schema unchanged. Diagnose version drift instead of using broad any or forced casts to hide it.

See financial functions, migration discipline and service boundaries.