hm-nodejs-database

Avoid calling Prisma inside loops. Use `include` or nested `select` to eager-load relations in one query, or batch fetch related records with `where: { id: { in: ids } }` and join them in memory with a Map.

Add a nullable `deletedAt` field to the model, then use Prisma middleware or Client Extensions to convert `delete` calls into updates setting `deletedAt`, and automatically filter out soft-deleted rows in `findMany` and `findFirst`.

`migrate dev` is for development: it creates migration files, applies them, and regenerates the client interactively. `migrate deploy` is non-interactive and only applies pending migrations, making it safe for CI/CD and production.

Use offset pagination for admin panels and numbered pages where jumping to a page is needed. Use cursor pagination for infinite scroll and large tables, since offset performance degrades as it scans skipped rows on big datasets.

Use `findUnique` when filtering by a primary key or a field with a `@unique` constraint, since Prisma optimizes these lookups. Use `findFirst` only for filters on non-unique fields, such as combining a business key with `deletedAt: null`.

`db push` syncs the schema directly without creating migration files, so changes are untracked and can cause irreversible data loss. Production deployments should always use `migrate deploy` with versioned migration files.