Data access
Type-safe ORM migrations keep PostgreSQL schemas aligned with NestJS services.
Prisma schema defines bookings, fleet, partners, and finance tables with strict relations.
Generated client types flow into NestJS services — eliminating stringly-typed SQL in business logic.
Migrations version database changes alongside pull requests for reviewable rollouts.
Engineers update schema.prisma with new fields and indexes.
prisma migrate produces SQL reviewed in CI before deploy.
Containers run migrations then boot NestJS with matching client version.
Compile-time types catch missing includes before production.
Relation graphs reveal cascade impacts when renaming entities.
New developers read schema instead of tribal SQL knowledge.
Services never construct raw SQL with user input — Prisma parameterizes queries.
Database roles separate migration users from application read/write users.
PrismaService wraps clients per request with tenant filters injected in repository layers.
Seed scripts bootstrap demo tenants for sandbox partners without touching production.
Statuses, passengers, and pricing lines model complex chauffeur trips.
Ledger tables link trips to payout batches with foreign keys.
Immutable audit rows reference actors without nullable chaos.
