Alberto Schiabel
Alberto Schiabel
Note: the generator is now called `prisma-client`.
Hi @pasha-vuiko, thanks for this PR! Can we please ask you to fix the [clippy tests](https://github.com/prisma/prisma-engines/actions/runs/11386262437/job/32467447451?pr=5009)?
Hi @jacobakkerboom and @vladfaust. We've recently changed the output we display on `prisma generate`'s success. Can you please try again via a recent Prisma version (e.g., 5.18+, the latest one...
Hi @jacobakkerboom, thanks, [http://pris.ly/d/importing-client](http://pris.ly/d/importing-client) accidentally slipped through. I'm pushing a fix now.
ESM (.mjs) modules of TypedSQL client use CommonJS imports when generating to a non-default location
Hey @solarisn and others, can you please try using the new `prisma-client` generator ([docs](https://www.prisma.io/docs/orm/prisma-schema/overview/generators#prisma-client-early-access))? It supports ESM as a first-class citizen. It's still experimental, and requires a custom output path...
ESM (.mjs) modules of TypedSQL client use CommonJS imports when generating to a non-default location
Here's an example using the `prisma-client` generator + the `typedSql` preview feature: https://github.com/prisma/prisma-examples/pull/8258
**DEPRECATED, SEE NEXT COMMENT.** This is what I have been able to reproduce so far, without knowing the schema. The migrations don't yield an `ALTER TABLE` statement, but they yield...
Ok, I'm now able to reproduce this issue, which seems to happen whenever `unique` constraints are applied to foreign keys. Reproduction steps: - Create a `docker-compose.yml` file with the following...
Hey @alan910127, can you please share your Prisma schemas?
> it almost looks like 5.19.0 is getting confused around the nested where clause an expecting fieldName on modelName instead? Hi @callumJPritchard, please open a new issue for that. You're...