Opened 17 years ago

Closed 17 years ago

#5460 closed (fixed)

unique_together should accept a single tuple for convenience

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

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 17 years ago.
A proper patch now, normalizing unique_together to a tuple of tuples

Download all attachments as: .zip

Change History (6)

comment:1 by deryck, 17 years ago

Owner: changed from nobody to deryck
Status: new → assigned

comment:2 by deryck, 17 years ago

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

by deryck, 17 years ago

Attachment: unique_together_single_tuple.diff​ added

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

comment:3 by deryck, 17 years ago

Has patch: set
Triage Stage: Unreviewed → Ready for checkin

comment:4 by Adrian Holovaty, 17 years ago

I'm about to check this in.

comment:5 by Adrian Holovaty, 17 years ago

Resolution: → fixed
Status: assigned → closed

(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