Introspecting enum fields

[mkieblesz]

At the moment kysely-codegen is not introspecting checks in postgres dialect.

Following table:

CREATE TABLE "example" (
    "id" bigserial PRIMARY KEY,
    "status" text CHECK ("status" IN ("public", "restricted", "private")) NOT NULL DEFAULT "restricted",
)

becomes

export interface Example {
  id: Generated<Int8>;
  status: Generated<string>;
}

while it should be

export interface Example {
  id: Generated<Int8>;
  status: Generated<'public' | 'restricted' | 'private'>;
}

I didn't take a look at the codebase yet, so if you could point me to the right direction I could implement that. Thanks!

ps. useful take on ENUMS vs CHECKS https://stackoverflow.com/a/10984951/11060504

Upvote & Fund

• We're using Polar.sh so you can upvote and help fund this issue.
• We receive the funding once the issue is completed & confirmed by you.
• Thank you in advance for helping prioritize & fund our backlog.

[KenParsons]

I came here to suggest similar, but specifically because of SQLite and its lack of an enum type or similar. The CHECK approach is basically the only way to get the same behavior, so making this improvement would be a huge boon for SQLite users.