-
Notifications
You must be signed in to change notification settings - Fork 42
UNIQUE constraint on columns #660
Copy link
Copy link
Closed
Labels
0. Needs triagePending approval or rejection. This issue is pending approval.Pending approval or rejection. This issue is pending approval.discussionBeing discussedBeing discussedenhancementNew feature or requestNew feature or request
Metadata
Metadata
Assignees
Labels
0. Needs triagePending approval or rejection. This issue is pending approval.Pending approval or rejection. This issue is pending approval.discussionBeing discussedBeing discussedenhancementNew feature or requestNew feature or request
Type
Fields
Give feedbackNo fields configured for issues without a type.
Is your feature request related to a problem? Please describe.
I can't specify that a column's values need to be unique. If Tables is to be considered anything like a database, then this would be essential.
Describe the solution you'd like
Just like there's a "required" switch on the column creation dialog (NOT NULL), a "unique" switch should be there too. Row creation should fail if the value is not unique.
Describe alternatives you've considered
No response
Additional context
No response