You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using prisma-extension-kysely pretty extensively. I have noticed that the stack trace thrown from any wrong query doesn't show the stack trace from my project. For example
const prismaKysely = prisma.$extends(
kyselyExtension({
kysely: (driver) =>
new Kysely({
dialect: {
createDriver: () => driver,
createAdapter: () => new MysqlAdapter(),
createQueryCompiler: () => new MysqlQueryCompiler(),
createIntrospector: (db) => new MysqlIntrospector(db)
}
})
})
);
If I do
await prismaKysely.$kysely
.selectFrom("users1" as any)
.where("id", "=", 0)
.select("id")
.execute();
Which is a totally wrong query, the stack only shows the error inside the prisma client, not the project.
The text was updated successfully, but these errors were encountered:
I am using prisma-extension-kysely pretty extensively. I have noticed that the stack trace thrown from any wrong query doesn't show the stack trace from my project. For example
const prismaKysely = prisma.$extends(
kyselyExtension({
kysely: (driver) =>
new Kysely({
dialect: {
createDriver: () => driver,
createAdapter: () => new MysqlAdapter(),
createQueryCompiler: () => new MysqlQueryCompiler(),
createIntrospector: (db) => new MysqlIntrospector(db)
}
})
})
);
If I do
await prismaKysely.$kysely
.selectFrom("users1" as any)
.where("id", "=", 0)
.select("id")
.execute();
Which is a totally wrong query, the stack only shows the error inside the prisma client, not the project.
The text was updated successfully, but these errors were encountered: