Allow string argument when regexp- or like-ing an enum column

[twiddler]

When filtering an enum column, e.g.

interface Database {
  Pet: {
    species: "dog" | "cat" | "hamster";
  };
}

with "regexp" or "like"

db.selectFrom("Pet")
  .where("species", "regexp", "ste") // ❌ Argument of type '"ste"' is not assignable to parameter of type 'OperandValueExpressionOrList<Database, "Pet", "species">'.(2345)
  .where("species", "like", "%ste%") // ❌ Argument of type '"%ste%"' is not assignable to parameter of type 'OperandValueExpressionOrList<Database, "Pet", "species">'.(2345)

the types leading to the type errors above seem too strict to me.

What do you think about broadening the type to string for the right-hand side argument of "regexp" and "like"?

Playground link

[koskimas]

This is related to #1333. As explained there, we don't currently have any operator spcific behavior. But this is definitely another case where it's needed.

You can get around this issue using something like this https://kyse.link/VjgoI