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
Unfortunately prisma-kysely generates the array type that the prisma client would return, but in reality the migration/shape prisma would use for this is actually a string, and it's stored as an arbitrary string format: {FOO,BAR}. An empty array would be stored as the string {}
Of course I wouldn't expect kysely to be selecting this string value as an array, so I think it would make the most sense for prisma-kysely to either say "we don't support enum array types" or (ideally) have it generate this array to a string type.
With postgres as a datasource, prisma will let you use an enum array as a value. Example:
Unfortunately
prisma-kysely
generates the array type that the prisma client would return, but in reality the migration/shape prisma would use for this is actually a string, and it's stored as an arbitrary string format:{FOO,BAR}
. An empty array would be stored as the string{}
Of course I wouldn't expect kysely to be selecting this string value as an array, so I think it would make the most sense for prisma-kysely to either say "we don't support enum array types" or (ideally) have it generate this array to a string type.
Here's an example of what we could generate:
The text was updated successfully, but these errors were encountered: