Helix
Helix
Explore posts from servers
PPrismaTTCTheo's Typesafe CultDTDrizzle TeamBABetter Auth
PostsComments
PPrisma
Created by Helix on 11/18/2024 in #help-and-questions
Two Schemas but only one will stay generated at a time
It is not, I can send you over a zip file of the project, or I can make it public temporarily. I can also send over any files you need.
19 replies
PPrisma
Created by Helix on 11/18/2024 in #help-and-questions
Two Schemas but only one will stay generated at a time
Almost like it wouldn’t install properly but it was installed and I could see it in my node_modules
19 replies
PPrisma
Created by Helix on 11/18/2024 in #help-and-questions
Two Schemas but only one will stay generated at a time
It was failing to import in my next.config.js
19 replies
PPrisma
Created by Helix on 11/18/2024 in #help-and-questions
Two Schemas but only one will stay generated at a time
Any ideas?
19 replies
PPrisma
Created by Helix on 11/18/2024 in #help-and-questions
Two Schemas but only one will stay generated at a time
I have tried the fix in the error logs but it fails to import the monorepo fix in the next.config.js
19 replies
PPrisma
Created by Helix on 11/18/2024 in #help-and-questions
Two Schemas but only one will stay generated at a time
I forgot to import the client from the outputs. I'm having a new issue though, whenever I try to deploy my site to heroku I am getting 
 2024-11-21T20:08:41.878893+00:00 app[web.1]: PrismaClientInitializationError: 
2024-11-21T20:08:41.878904+00:00 app[web.1]: Invalid `prisma.user.findUnique()` invocation:
2024-11-21T20:08:41.878904+00:00 app[web.1]: 
2024-11-21T20:08:41.878905+00:00 app[web.1]: 
2024-11-21T20:08:41.878905+00:00 app[web.1]: Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x".
2024-11-21T20:08:41.878905+00:00 app[web.1]: 
2024-11-21T20:08:41.878906+00:00 app[web.1]: We detected that you are using Next.js, learn how to fix this: https://pris.ly/d/engine-not-found-nextjs.
2024-11-21T20:08:41.878906+00:00 app[web.1]: 
2024-11-21T20:08:41.878909+00:00 app[web.1]: This is likely caused by a bundler that has not copied "libquery_engine-debian-openssl-3.0.x.so.node" next to the resulting bundle.
2024-11-21T20:08:41.878909+00:00 app[web.1]: Ensure that "libquery_engine-debian-openssl-3.0.x.so.node" has been copied next to the bundle or in "node_modules/@internal/aero/client".
 2024-11-21T20:08:41.878893+00:00 app[web.1]: PrismaClientInitializationError: 
2024-11-21T20:08:41.878904+00:00 app[web.1]: Invalid `prisma.user.findUnique()` invocation:
2024-11-21T20:08:41.878904+00:00 app[web.1]: 
2024-11-21T20:08:41.878905+00:00 app[web.1]: 
2024-11-21T20:08:41.878905+00:00 app[web.1]: Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x".
2024-11-21T20:08:41.878905+00:00 app[web.1]: 
2024-11-21T20:08:41.878906+00:00 app[web.1]: We detected that you are using Next.js, learn how to fix this: https://pris.ly/d/engine-not-found-nextjs.
2024-11-21T20:08:41.878906+00:00 app[web.1]: 
2024-11-21T20:08:41.878909+00:00 app[web.1]: This is likely caused by a bundler that has not copied "libquery_engine-debian-openssl-3.0.x.so.node" next to the resulting bundle.
2024-11-21T20:08:41.878909+00:00 app[web.1]: Ensure that "libquery_engine-debian-openssl-3.0.x.so.node" has been copied next to the bundle or in "node_modules/@internal/aero/client".
this error now.
19 replies
PPrisma
Created by Helix on 11/18/2024 in #help-and-questions
Two Schemas but only one will stay generated at a time
I figured it out!
19 replies
PPrisma
Created by Helix on 11/18/2024 in #help-and-questions
Two Schemas but only one will stay generated at a time
export const aero_db = new PrismaClient({
    datasources: { db: { url: env.DATABASE_URL } },
});
export const alec_site_db = new PrismaClient({
    datasources: { db: { url: env.ALEC_SITE_DB_URL } },
});
export const aero_db = new PrismaClient({
    datasources: { db: { url: env.DATABASE_URL } },
});
export const alec_site_db = new PrismaClient({
    datasources: { db: { url: env.ALEC_SITE_DB_URL } },
});
this is the prisma clients
19 replies
PPrisma
Created by Helix on 11/18/2024 in #help-and-questions
Two Schemas but only one will stay generated at a time
// schema1.prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["driverAdapters", "prismaSchemaFolder", "multiSchema"]
  output          = "../node_modules/@internal/prisma-first/client"
}

datasource db {
  provider = "mysql"
  url      = env("DATABASE_URL")
} 

// schema2.prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["driverAdapters", "prismaSchemaFolder", "multiSchema"]
  output          = "../node_modules/@internal/prisma-second/client"
}

datasource db {
  provider = "mysql"
  url      = env("ALEC_SITE_DB_URL")
}
// schema1.prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["driverAdapters", "prismaSchemaFolder", "multiSchema"]
  output          = "../node_modules/@internal/prisma-first/client"
}

datasource db {
  provider = "mysql"
  url      = env("DATABASE_URL")
} 

// schema2.prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["driverAdapters", "prismaSchemaFolder", "multiSchema"]
  output          = "../node_modules/@internal/prisma-second/client"
}

datasource db {
  provider = "mysql"
  url      = env("ALEC_SITE_DB_URL")
}
I have two different database schemas one called aero and one called alec_site that I'm trying to connect to, aero contains the user data & app specific data where alec_site contains other data that I need. I'm not getting any specific errors besides Property 'vendor_id_walmart' does not exist on type 'PrismaClient<{ datasources: { db: { url: string; }; }; }, never, DefaultArgs>'. for the alec_site db.
19 replies