Aladin El-Khalil
Aladin El-Khalil
PPrisma
Created by Aladin El-Khalil on 9/30/2024 in #help-and-questions
Error validating datasource URL must start with the protocol prisma://
@Nurul (Prisma)
10 replies
PPrisma
Created by Aladin El-Khalil on 9/30/2024 in #help-and-questions
Error validating datasource URL must start with the protocol prisma://
I recall that the cli build command encourages the use of --no-engine in production, that's confusing then?
10 replies
PPrisma
Created by Aladin El-Khalil on 9/30/2024 in #help-and-questions
Error validating datasource URL must start with the protocol prisma://
I think that solved the problem. Why did that help @Nurul (Prisma) ?
10 replies
PPrisma
Created by Aladin El-Khalil on 9/30/2024 in #help-and-questions
Error validating datasource URL must start with the protocol prisma://
Yes I'll try
10 replies
PPrisma
Created by Aladin El-Khalil on 9/30/2024 in #help-and-questions
Error validating datasource URL must start with the protocol prisma://
Hi @Nurul (Prisma) I'm generating with the command npx prisma generate --no-engine My full build command on Vercel is next build && npx prisma generate --no-engine I'm not using accelerate, it's commented out. This is my prisma client.
import { PrismaClient } from "@prisma/client";
// import { withAccelerate } from "@prisma/extension-accelerate";

const createAcceleratedPrismaClient = () => {
return new PrismaClient({
log:
process.env.NODE_ENV === "development"
? // ? ["query", "error", "warn"]
["error", "warn"]
: ["error"],
});
// .$extends(withAccelerate());
};

type PrismaClientAccelerated = ReturnType<typeof createAcceleratedPrismaClient>;

const globalForPrisma = globalThis as unknown as {
prisma: PrismaClientAccelerated | undefined;
};

let prisma = globalForPrisma.prisma ?? createAcceleratedPrismaClient();

if (process.env.NODE_ENV !== "production") {
globalForPrisma.prisma = prisma;
}

export default prisma;
import { PrismaClient } from "@prisma/client";
// import { withAccelerate } from "@prisma/extension-accelerate";

const createAcceleratedPrismaClient = () => {
return new PrismaClient({
log:
process.env.NODE_ENV === "development"
? // ? ["query", "error", "warn"]
["error", "warn"]
: ["error"],
});
// .$extends(withAccelerate());
};

type PrismaClientAccelerated = ReturnType<typeof createAcceleratedPrismaClient>;

const globalForPrisma = globalThis as unknown as {
prisma: PrismaClientAccelerated | undefined;
};

let prisma = globalForPrisma.prisma ?? createAcceleratedPrismaClient();

if (process.env.NODE_ENV !== "production") {
globalForPrisma.prisma = prisma;
}

export default prisma;
10 replies
PPrisma
Created by Aladin El-Khalil on 9/30/2024 in #help-and-questions
Error validating datasource URL must start with the protocol prisma://
@Jon Harrell Here you go, a new post, thanks for the help in advance!
10 replies
PPrisma
Created by Faith on 4/24/2024 in #help-and-questions
Error validating datasource `db`: the URL must start with the protocol `prisma://`
I'm new on Discord. Used the search bar to find this post. Wasn't sure if I'm supposed to continue the discussion here or start a new post.
17 replies
PPrisma
Created by Faith on 4/24/2024 in #help-and-questions
Error validating datasource `db`: the URL must start with the protocol `prisma://`
No description
17 replies
PPrisma
Created by Faith on 4/24/2024 in #help-and-questions
Error validating datasource `db`: the URL must start with the protocol `prisma://`
Hello @Jon Harrell, I'm having the same issue error when deploying my Next application to Vercel. Everything works fine locally. I have triple-checked env variables on Vercel and they're the same as my env locally. I also get this error if I build the project and run prod environment locally without deploying to Vercel. Any idea what might cause this; and how to solve it?
17 replies