Registry / database / prisma-generator-dotnet-postgres

prisma-generator-dotnet-postgres

library2.2.5jsnpmunverified

Prisma generator that produces .NET Postgres data models (C# classes) from your Prisma schema. Current stable version 2.2.5, release cadence irregular. Differentiators: generates DbContext with EF Core mappings, handles relations and enums, opinionated naming conventions. Use when you need to keep .NET models in sync with Prisma schema without manual mapping.

database

npm install prisma-generator-dotnet-postgres

github ↗package ↗homepage ↗

INSTALL

IMPORT

SIG · PRISMA-GENERATOR-D

prisma-generator-dotnet-postgres

databasejavascriptv2.2.5

harness data pending

Install & Compatibility

Where this runs

No compatibility data collected yet for this library.

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

generator

✓ generator client { provider = "prisma-generator-dotnet-postgres" }

✗ generator client { provider = "dotnet-postgres" }

Add to schema.prisma generators block

Generated C# classes

✓ // Generated in output path after `npx prisma generate`

✗ // Don't manually edit generated files

Files are regenerated on each prisma generate

NuGet package

✓ dotnet add package Prisma.Generator.Dotnet.Postgres

✗ Install-Package Prisma.Generator.Dotnet.Postgres

Optional but provides runtime helpers

Shows Prisma schema generator config and sample models that produce C# classes

// schema.prisma generator dotnet_postgres { provider = "prisma-generator-dotnet-postgres" output = "../dotnet-app/Models" namespace = "MyApp.Models" } model User { id Int @id @default(autoincrement()) name String posts Post[] } model Post { id Int @id @default(autoincrement()) title String author User @relation(fields: [authorId], references: [id]) authorId Int } // Run: npx prisma generate

Debug

Known issues

breakingGenerator output path must be outside node_modules or generated files may be overwritten

fix

Set output to a directory in your .NET project

affects: >=1.0

deprecatedVersion 1.x used different namespace format; upgrade schema

fix

Update generator block to use 'namespace' field instead of 'nameSpace'

affects: <2.0

gotchaEnum models require manual DbContext configuration for PostgreSQL enums

fix

Add .HasPostgresEnum() in OnModelCreating

affects: >=2.0

gotchaRelation properties generate as virtual ICollection<T>; lazy loading not enabled by default

fix

Add UseLazyLoadingProxies() if needed

affects: >=2.0

Errors

Common errors & fixes

Error: Cannot find module 'prisma-generator-dotnet-postgres'

Package not installed locally

fix

npm install -D prisma-generator-dotnet-postgres

Generator 'dotnet_postgres' not found

Incorrect provider name in schema.prisma

fix

Use provider = "prisma-generator-dotnet-postgres"

The namespace 'MyApp.Models' could not be found

Output path not added to .NET project

fix

Add <ProjectReference> or include files manually

Upgrade

Version history

2.2.5latest on npm

Audit

Dependencies

prismarequiredPeer dependency for generating models

Agent activity

5 hits · last 30 days

node

Resources

githubhttps://github.com/rokkitclub/astolfo ↗

packageprisma-generator-dotnet-postgres ↗

homepagehttps://github.com/rokkitclub/astolfo#readme ↗