Django

Code

Ticket #5460 (closed: fixed)

Opened 1 year ago

Last modified 1 year ago

unique_together should accept a single tuple for convenience

Reported by: deryck Assigned to: deryck
Milestone: Component: Core framework
Version: SVN Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: 1 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

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

unique_together_single_tuple.diff (1.4 kB) - added by deryck on 09/14/07 15:26:23.
A proper patch now, normalizing unique_together to a tuple of tuples

Change History

09/14/07 11:30:04 changed by deryck

  • owner changed from nobody to deryck.
  • needs_better_patch changed.
  • status changed from new to assigned.
  • needs_tests changed.
  • needs_docs changed.

09/14/07 12:05:09 changed by deryck

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

09/14/07 15:26:23 changed by deryck

  • attachment unique_together_single_tuple.diff added.

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

09/14/07 15:27:28 changed by deryck

  • has_patch set to 1.
  • stage changed from Unreviewed to Ready for checkin.

09/14/07 15:29:58 changed by adrian

I'm about to check this in.

09/14/07 15:36:53 changed by adrian

  • status changed from assigned to closed.
  • resolution set to fixed.

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

Add/Change #5460 (unique_together should accept a single tuple for convenience)




Change Properties
Action