Serhii Tatarintsev
Serhii Tatarintsev
This issue is fixed and will be available in Prisma 5.1
Internal note: https://www.notion.so/prismaio/Timezone-issues-in-query-engine-and-client-a1a2a9c6096a49f9a63db50c4c68bfe6
Hi @romanwbruce . Could you provide the complete schema? IT is missing `pitch` model present in your query. Also, it would be really helpful if you can provide a sample...
So, we've actually not only reproduced it, but fixed it and the PR that was posted in https://github.com/prisma/prisma/issues/13134#issuecomment-1257956062 made it into Prisma 4.5.0 ([PR](https://github.com/prisma/prisma-engines/pull/3242)). I've just re-run my reproduction from...
Hey @bingomanatee , With the lack of information and our inability to reproduce this issue, we're now closing it. Feel free to comment if you have any updates about it....
@Jolg42 not yet, will fix it in the coming days
Hi @Jevinambaliya26. Could you try with more recent prisma version? 3.15.2 is a year old at this point, we did quite a bunch of fixes in the meantime, including platform...
@pheuter could you open a separate issue and share more of your schema? At the very least, non-abbreviated `Payroll` model and all the models and composites it references. Snippet you've...
@semoal noted the bug (#18549). Until it is fixed, you can replace `markedId: { in: "value" }` part in your test with either `marketId: "value"` or `markedId: { in: ["value"]...
@yharaskrik please, share full schema and the prisma call so we could reproduce it. Thank you!