Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#18092 closed New feature (duplicate)

Composite indexes

Reported by: Ivan Virabyan Owned by: nobody
Component: Database layer (models, ORM) Version: 1.4
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

The patch adds support for composite indexes. Usage:

class Post(models.Model):
	creator = models.ForeignKey(User)
	date_published = models.DateTimeField()

	class Meta:
		composite_indexes = (('creator', 'date_published'),)

Attachments (1)

composite_indexes.diff​ (3.8 KB ) - added by Ivan Virabyan 14 years ago.

Download all attachments as: .zip

Change History (5)

by Ivan Virabyan, 14 years ago

Attachment: composite_indexes.diff​ added

comment:1 by Ivan Virabyan, 14 years ago

Just thought that index_together might be a better name, for consistency with unique_together

comment:2 by anonymous, 14 years ago

Something like this is certainly needed

comment:3 by Anssi Kääriäinen, 14 years ago

Resolution: → duplicate
Status: new → closed

This seems like a duplicate of #5805. FWIW I agree that this would be a nice addition.

comment:4 by Ivan Virabyan, 14 years ago

Thanks for pointing out! Searching didn't give me any results on this issue.

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