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
In drizzle, we usually give the check constraints names when declaring check constraints, check("age_check1", sql${table.age} > 21). In postgresql command, you don't have to. You just declare check constraints and let postgresql define the name of the constraints.
Can we let postgresql define the name of the constraints instead of we doing it ourselves?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In drizzle, we usually give the
check
constraints names when declaring check constraints,check("age_check1", sql
${table.age} > 21)
. In postgresql command, you don't have to. You just declarecheck
constraints and let postgresql define the name of the constraints.Can we let postgresql define the name of the constraints instead of we doing it ourselves?
Beta Was this translation helpful? Give feedback.
All reactions