add-prisma-model

To scaffold a Prisma model, you automate schema updates by enforcing project conventions like snake_case mappings and BigInt for monetary fields. This generates a migration-ready model skeleton aligned with your existing database guidelines.

Best practices for adding BigInt fields to a Prisma schema involve using the BigInt type for monetary values like Lovelace. Enforcing this convention during model scaffolding ensures large numerical values map correctly to your PostgreSQL database without precision loss.

To set up relations during a database migration, you read the existing Prisma schema to ensure compatibility with current models. Convention-driven scaffolding then guides you through adding proper relation fields, preparing a ready-to-migrate model that keeps your database in sync.

Yes, this Prisma scaffolding approach works with existing PostgreSQL schemas by reading the current schema file. It ensures compatibility with existing models, enums, and relationships before generating the new model skeleton and applying the database migration.

You should use snake_case mappings for Prisma model fields to maintain consistent naming conventions between your ORM schema and the underlying PostgreSQL database. Automating this during model creation prevents manual mapping errors and ensures database columns adhere to project standards.