Prepare statement throws type error for enums. How to get type safety for prepared values

the status column in the schema is an enum like so:

 status: mysqlEnum("status", "PENDING", "ACCEPTED", "DECLINED")
      .notNull()
      .default("PENDING"),

 status: mysqlEnum("status", "PENDING", "ACCEPTED", "DECLINED")
      .notNull()
      .default("PENDING"),

 status: mysqlEnum("status", "PENDING", "ACCEPTED", "DECLINED")
      .notNull()
      .default("PENDING"),

 status: mysqlEnum("status", "PENDING", "ACCEPTED", "DECLINED")
      .notNull()
      .default("PENDING"),

and even type casting the placeholder does not work

  db.update(table).set({ status: sql.placeholder("status") as Status })

  db.update(table).set({ status: sql.placeholder("status") as Status })

  db.update(table).set({ status: sql.placeholder("status") as Status })

  db.update(table).set({ status: sql.placeholder("status") as Status })

is there a proper way to get type safety in general for prepared statements?

Love the performance gains, but really bums me out that I loose all safeguards regarding types

Angelelz•12/4/23, 2:26 PM

Check this typescript playground for a workaround

Angelelz•12/4/23, 2:26 PM

https://www.typescriptlang.org/play?noErrorTruncation=true#code/JYWwDg9gTgLgBAbzgEysAXugNgUzgXzgDMoIQ4AiVDbHAWmhAHoQBPAZwEcsAmCgKFCRYiOGy5YAKgEMARrgA0cAG7SoAYwAWapeO4BRAHYBXcoRJlK1TLgZRmerHXXQcAodHhIJSgMoBFABkCYlJyKjQbekYBfhdDdnhE6Rhjdhx2OABeOABtCgAFfQA5ABEASWKAcQolCgBBAGFG-QLJfVLaylL9RsDKjooAXThpTPjE-jiIBKSYFLTssQ4DExAACgpk1PYu7bSMgEp+OFOzgDpDCBhi4ywsdeOzi+QcImk7mE2issqa4-4MFYYDwvnmOyWQJBECIcH27CmE3g83kOHqS0cMlRmxRuAA+tIuggTnBgMgAFwqNRaNSbMlEuC4QwAcxgmkpAGYAAz4Q7nMBoEBqVgAaRwrEeChJ8Mp8P4vIA3IiZokULIltZaOsEIQxqNDKwAchZOdjGBkCkcOtcWi+ekvt5wWlZdx+VhpOocJoIFhXlBNvCKIdRpljIYANZXADuhhDcACgQAPIk0CyAHynXlAA

TS Playground - An online editor for exploring TypeScript and JavaS...

The Playground lets you write TypeScript or JavaScript online in a safe and sharable way.

Angelelz•12/4/23, 2:26 PM

Can create a new GH issue for this?

AAngelelz https://www.typescriptlang.org/play?noErrorTruncation=true#code/JYWwDg9gTgLgBAbz...

HocusOP•12/4/23, 2:33 PM

thanks, that works for now. I assume I didn't miss anything in the docs then and there is no better/type-safe way for prepared statements, like generics or something?

AAngelelz Can create a new GH issue for this?

HocusOP•12/4/23, 2:34 PM

yea I can add an issue for this

Angelelz•12/4/23, 2:35 PM

We just need to add the placeholder type to the mysqlEnummysqlEnum type

HocusOP•12/4/23, 2:45 PM

ok.

It would be cool in general to get some typesafety for the prepared statements, specially for the object that is passed to the execute({...})execute({...}) argument.

Angelelz•12/4/23, 2:50 PM

There is an open issue for that, we just haven't been able to get to that one yet

AAngelelz There is an open issue for that, we just haven't been able to get to that one ye...

HocusOP•12/5/23, 11:18 AM

https://github.com/drizzle-team/drizzle-orm/issues/1608

GitHub

[BUG]: `sql.placeholder` throws type error for enums · Issue #1608 ...

What version of drizzle-orm are you using? 0.29.1 What version of drizzle-kit are you using? 0.20.6 Describe the Bug sql.placeholder throws type error for enums. import { drizzle } from "drizz...

Prepare statement throws type error for enums. How to get type safety for prepared values

Similar Threads

Similar Threads

Similar Threads