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
I'm guessing the motivation for the current signature is to prevent 0-argument calls to on, which makes sense. If you adopted the suggestion, there would need to be some well-defined/document behavior for 0-argument calls (i.e., not make any constraint, throw an error, etc.).
Totally understand if you want to keep it the way it is, but wanted to make you aware of this use case in case you wanted to adopt the suggestion or had any other ideas to make it easier to do something like this.
Expected behavior
No response
Environment & setup
No response
The text was updated successfully, but these errors were encountered:
What version of
drizzle-orm
are you using?0.30.10
What version of
drizzle-kit
are you using?0.21.4
Describe the Bug
The pg
UniqueOnConstraintBuilder
has the following signature for theon
method:I want to do something like this (to keep my uniqueness constraint synced with a particular set of fields):
However, I get the error
Instead, I'm forced to do this:
It's not the worst thing in the world, but it would certainly be cleaner to do the former. This would be possible if the signature was instead
I'm guessing the motivation for the current signature is to prevent 0-argument calls to
on
, which makes sense. If you adopted the suggestion, there would need to be some well-defined/document behavior for 0-argument calls (i.e., not make any constraint, throw an error, etc.).Totally understand if you want to keep it the way it is, but wanted to make you aware of this use case in case you wanted to adopt the suggestion or had any other ideas to make it easier to do something like this.
Expected behavior
No response
Environment & setup
No response
The text was updated successfully, but these errors were encountered: