Opened 9 years ago

Closed 9 years ago

#5460 closed (fixed)

unique_together should accept a single tuple for convenience

Reported by: deryck Owned by: deryck
Component: Core (Other) Version: master
Severity: Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

While working on #4928 which seems invalid, the idea came up that unique_together should allow a single tuple rather than a tuple of tuples for convenience.

Attachments (1)

unique_together_single_tuple.diff (1.4 KB) - added by deryck 9 years ago.
A proper patch now, normalizing unique_together to a tuple of tuples

Download all attachments as: .zip

Change History (6)

comment:1 Changed 9 years ago by deryck

Needs documentation: unset
Needs tests: unset
Owner: changed from nobody to deryck
Patch needs improvement: unset
Status: newassigned

comment:2 Changed 9 years ago by deryck

gah! I only added a patch for validation, not the feature itself. Working on that now....

Changed 9 years ago by deryck

A proper patch now, normalizing unique_together to a tuple of tuples

comment:3 Changed 9 years ago by deryck

Has patch: set
Triage Stage: UnreviewedReady for checkin

comment:4 Changed 9 years ago by Adrian Holovaty

I'm about to check this in.

comment:5 Changed 9 years ago by Adrian Holovaty

Resolution: fixed
Status: assignedclosed

(In [6213]) Fixed #5460 -- unique_together now accepts a single tuple for convenience. Thanks, Deryck Hodge

Note: See TracTickets for help on using tickets.
Back to Top