Jan Piotrowski comments

Results 2422 comments of


                                            Jan Piotrowski

Improve Timezone Support for Existing MySQL Databases configured with a Non-UTC Timezone

Ping @jhaemin about Divy's last followup. We want to move this issue forward, but need your help.

Type incompatible for relation id fields: `Type 'string' is not assignable to type 'never'`

Can someone provide more information that would allow us to reproduce? In the original post the relevant `list` was missing (I would say, right?) and the two comments include no...

Type incompatible for relation id fields: `Type 'string' is not assignable to type 'never'`

On a quick skim your issue does not have any similarities with the originally reported one here, except that there is a "not assignable to type" error message - but...

`SELECT FOR UPDATE`

Potentially related: https://github.com/prisma/prisma/issues/17136 https://github.com/prisma/prisma/issues/5983

Update to present behavior: Error message for @phryneas' schema now looks like this: ``` C:\Users\Jan\Documents\throwaway\divyPgBouncer>prisma generate Error: Schema parsing error: Error validating model "Post": Automatic related field generation would cause...

When using a `connect` or `create` block in a `create()` or `update()`, other scalar relation fields cannot be used directly

We can do that, but I expect this to be a limitation of the system right now. Did I follow the issue correctly that this applies both a) when using...

When using a `connect` or `create` block in a `create()` or `update()`, other scalar relation fields cannot be used directly

Let's update the issue title then :D

Fix Insiders versioning with Prisma 3.x

Did not actually become a problem yet because of: https://github.com/prisma/language-tools/issues/867

Support `@writable(false)` or `@readonly`

No, we only communicate our priorities via our roadmap on https://pris.ly/roadmap and do not give further ETAs, except sometimes via activity in issues that we are actively looking into. I...

`prisma migrate resolve --applied` not working on new project, `migration ... could not be found.` when using PowerShell on Windows

So your project now has a `prisma/migrations/0_init` folder with a `migration.sql` file in it? Are you excecuting the `npx prisma migrate resolve --applied` command in the root of your project?...