Prisma

P

Prisma

The official Discord server of Prisma! Find us online at prisma.io

Join

Handling @db.Date fields client side from different Timezones (Postgres)

We have a database where some tables have date only fields (DateTime @db.Date) while others are regular DateTime fields. When the server sends this data then javscript will create a new Date() for both since we don't have a date only primitive there. This causes the @db.Date field which is stored as 2025-04-20 to be understood as a UTC 00:00 date. Therefore if I'm in New York which is -4h the date will result in 2020-04-19T20.00.000Z and the data will shift by one day in something like a calendar. We COULD simply say that all dates that we receive client side we add the current timezones offset so that it will then be correctly parsed as 2020-04-20T00.00.000Z. Then we woulc correctly have the beginning of the DB's date in the local timezone to correctly sort in the entry, BUT then we would mess up regular DateTime dates. A "createdAT" timestamp from 14:00 local NY time will come back to the same client with a 18:00 time which is WRONG....

Schema Troubleshooting

Hi everyone, i have a pretty simple Schema with three models. However, whenever i try to push the schema to my MYSQL DB, i keep running into foriegn key restraints. I don't see anything wrong with my relations thats causing this to occur. One thing to note is that i did accidentally migrate the schema to my db, but i went and dropped the table and the migration folder. Did I make a silly syntax mistake that i'm missing, or will i need to baseline my db due to migrations being out of sync?

full Text Search not working with Postgres and Nextjs

Hello, I have a problem with trying to use Full Text Search with Prisma ORM. I have followed the guide in Prisma docs, but I still get this error. I posted a snapshot of prima file and the code we have in the docs.
...
No description

SvelteKit __dirname is not defined in ES module scope

``` ReferenceError: __dirname is not defined in ES module scope This file is being treated as an ES module because it has a '.js' file extension and '/package.json' contains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension. at requireLibrary (file:///server/chunks/_server.ts-C8y8rTjF.js:51:5556) at file:///server/chunks/_server.ts-C8y8rTjF.js:221:21...

Enum mapped values in typedSQL

Hi! 👋 I’m having trouble using enums with mapped values in typedSql. Here’s what I have: ``` enum Status {...

Generate command not working

nwb-launcher@0.1.0 db:generate C:...\gitrepos\repo prisma generate
Environment variables loaded from .env Prisma schema loaded from prisma\schema.prisma...
Solution:
Solved, it did not like my output folder

prisma migrate dev (prisma+postgres://accelerate.prisma-data) P1011: Error opening a TLS connection

Hi team, I have setup a prisma-data db and recently I'm getting error when prisma migrate, don't know if it's something of my computer setup or it's happening to others. pnpm prisma migrate dev Environment variables loaded from .env...

Why do I have both `@prisma/client` and `generated/prisma/client` in my import suggestions?

Hello, first off the docs say: "The install command invokes prisma generate for you which reads your Prisma schema and generates a version of Prisma Client that is tailored to your models."...

go sdk?

big fan of yours, theres a chance to see this is go ?

Parallel Table Names using MuliSchema feature

I'm in the process of deploying some parallel models to new schemas so that we have a sandbox schema to work with until we're ready to do some data migration. I've learned that using the multischema feature doesn't include the schema name as part of the contraint names, so I've had to go through and use the map() function to rename all of my contraints so that they're namespaced to my new schema (e.g. {tablename}_{column_names}_fkey --> {schemaName}_{tablename}_{column_names}_fkey this has allowed me to deploy the parallel tables in a new schema, however when i reun npx prisma migrate dev i still have some outstanding changes that it's trying to apply and I can't figure out what i'm doing wrong or how to rememdy the issue. Curious if anybody has encountered issues with somethign like this ``` Drift detected: Your database schema is not in sync with your migration history. The following is a summary of the differences between the expected database schema given your migrations files, and the actual schema of the database....

I would like to implement native support for timestamp precision

This ticket is exactly the issue that I've been having: https://github.com/prisma/prisma/issues/15516 I have the time and would like to complete it. If there's anyone that has experience contributing to similar changes to Schema mappings in relation to queries, any help intuitions on where to start / similar tickets to look at. Thank you!!...

prisma-client provider can't be used with multiple generators

When running the generate command I get an error: ``` │ Loaded Prisma config from ".....\prisma.config.ts". │ Prisma config detected, skipping environment variable loading. │ Prisma schema loaded from prisma\schema...

P1001: Can't reach database server at api.mydomain.com:5432

Been debugging this for hours, nothing works - I'm using the exact same connection string via Psql and it works, I've double check encoding, open port, password, dns resolution, everything

@prisma_client_runtime_library.js?v=16686fa7:135 Uncaught (in promise) TypeError: __banner_node_url.

I upgraded to prisma 6.6.0 and getting this error randomly this morning in my browser. I'm using Bun with a turbo monorepo ```generator client {...

Specifying postgres schema while using a postgres database url

We use prisma migrations with an application that uses kysely, and some direct postgres queries. The application stores its data in a named postgres schema. Our application initializes our postgres pool with a database url, stored in an env var. However, it seems that in order to use prisma with a postgres schema we must append ?schema={name} to the url that is used by prisma to get prisma to understand that it ought to operate in a schema....

panicked at query-engine\query-engine-node-api\src\engine. Failed to deserialize constructor options

Hi guys. I have a shared prisma package setup in one repo, and 2 other repositories (frontend and server) that use the shared prisma package. This setup has been working very fine for a long time. but just today i added a new table and deployed the updated package (something i do every week). and it's craching my servers....
No description

ERROR: ALTER COLUMN TYPE is only implemented in the declarative schema changer

Hi all, i have a serious issue. I can't seem to run npx prisma migrate dev safely. For some reason my migration history has a change that was implemented on the 20241006 (20241006150212_added_our_platform_fee_to_store) Theres a sequence of three migration files the first creates the "our_platform_fee" -- ALTER TABLE "Store" ADD COLUMN "our_platform_fee" DECIMAL(65,30) NOT NULL DEFAULT 0.05; Then there is a migration which changes the TYPE...
No description

db push not working with new prisma.config `migrate` adapter

hey guys, anyone got db push to work with turso? getting ```...

Prisma 6.6.0 ESM with Nx Monorepo - Typescript type check failures

The message is too long, so the rest of it is in the replies Prisma: 6.6.0 Repo: monorepo using NX and esbuild version: 20.6.2 Package manager: pnpm with workspaces Type: module (ESM and not CommonJS)...

Sudden connection string issues

Hi, I have been working the the ORM for a while now and for seemingly no reason I recently encountered issues with my instance. When sending any request this error is thrown:...