We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://orm.drizzle.team/docs/indexes-constraints
The examples in the docs for table constraints (unique, check, etc) show an object return syntax for the extraConfig callback:
export const userNulls = pgTable('user_nulls_example', { id: integer('id').unique("custom_name", { nulls: 'not distinct' }), }, (t) => ({ unq: unique().on(t.id).nullsNotDistinct() }));
looks like that syntax was deprecated by a commit for RLS about a month ago & now it expects an array return:
export const userNulls = pgTable('user_nulls_example', { id: integer('id').unique("custom_name", { nulls: 'not distinct' }), }, (t) => [ unique().on(t.id).nullsNotDistinct() ]);
would also be helpful to add a note or something for this change since it's breaking from how constraints used to work in drizzle
thanks!
The text was updated successfully, but these errors were encountered:
#466
Sorry, something went wrong.
No branches or pull requests
https://orm.drizzle.team/docs/indexes-constraints
The examples in the docs for table constraints (unique, check, etc) show an object return syntax for the extraConfig callback:
looks like that syntax was deprecated by a commit for RLS about a month ago & now it expects an array return:
would also be helpful to add a note or something for this change since it's breaking from how constraints used to work in drizzle
thanks!
The text was updated successfully, but these errors were encountered: