SvelteKit __dirname is not defined in ES module scope
Enum mapped values in typedSQL
Generate command not working
[email protected] db:generate C:...\gitrepos\repo prisma generateEnvironment variables loaded from .env Prisma schema loaded from prisma\schema.prisma...
prisma migrate dev (prisma+postgres://accelerate.prisma-data) P1011: Error opening a TLS connection
Why do I have both `@prisma/client` and `generated/prisma/client` in my import suggestions?
Parallel Table Names using MuliSchema feature
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
prisma-client provider can't be used with multiple generators
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
@prisma_client_runtime_library.js?v=16686fa7:135 Uncaught (in promise) TypeError: __banner_node_url.
Specifying postgres schema while using a postgres database url
?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

ERROR: ALTER COLUMN TYPE is only implemented in the declarative schema changer
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...
db push not working with new prisma.config `migrate` adapter
db push
to work with turso?
getting
```...Prisma 6.6.0 ESM with Nx Monorepo - Typescript type check failures
NX
and esbuild
version: 20.6.2
Package manager: pnpm with workspaces
Type: module (ESM and not CommonJS)...Sudden connection string issues
PostgreSQL Replica Identity Error Despite DEFAULT Setting
Sudden issues after trying to access localhost with my nextjs app - no changes in code.
Starter plan pay as you go