Opened 15 years ago

Closed 14 years ago

Last modified 12 years ago

#11702 closed Uncategorized (fixed)

ForeignKey validation should check that to_field is unique

Reported by: physicsnick Owned by: Marcos Moyano
Component: Database layer (models, ORM) Version: 1.1
Severity: Normal Keywords: pycamp2010
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: yes
Easy pickings: no UI/UX: no


Currently, ForeignKey validation does not check that to_field is unique. Here is an example:

class Author(models.Model): 
    code = models.CharField(max_length=10, db_index=True) 
    first_name = models.CharField(max_length=30) 
    last_name = models.CharField(max_length=40) 
class Book(models.Model): 
    title = models.CharField(max_length=100) 
    author = models.ForeignKey(Author, to_field='code')

Django happily accepts these models. For PostgresSQL and Oracle, foreign keys must be unique, but MySQL and SQLite make no such requirement. MySQL requires only that the column be indexed, and SQLite has no requirements (it does not enforce foreign key constraints).

Django requires uniqueness so it should be enforcing this on its own. The documentation of to_field should also specify that it should be unique.

Here is the relevant MySQL documentation:

...MySQL and InnoDB require that the referenced columns be indexed for performance. However, the system does not enforce a requirement that the referenced columns be UNIQUE or be declared NOT NULL.

Here is some extended discussion:

Attachments (2)

related.patch (1.8 KB ) - added by Marcos Moyano 14 years ago.
django.db.fields.related patch
new_patch.patch (2.7 KB ) - added by Marcos Moyano 14 years ago.
New patch

Download all attachments as: .zip

Change History (12)

comment:1 by Russell Keith-Magee, 14 years ago

milestone: 1.2
Triage Stage: UnreviewedAccepted

comment:2 by Marcos Moyano, 14 years ago

Owner: changed from nobody to Marcos Moyano
Status: newassigned

by Marcos Moyano, 14 years ago

Attachment: related.patch added

django.db.fields.related patch

comment:3 by Marcos Moyano, 14 years ago

A humble approach at related field initialization. Don't know how to write a test suite for this since it's on initialization. I've ran the test suite just to make sure nothing breaks.

comment:4 by Ramiro Morales, 14 years ago

Has patch: set
Keywords: pycamp2010 added
Patch needs improvement: set

by Marcos Moyano, 14 years ago

Attachment: new_patch.patch added

New patch

comment:5 by Marcos Moyano, 14 years ago

Resolution: fixed
Status: assignedclosed

New patch. Moved validation code to and add test suite.

I think the validation could be clearear and simpler if we add a line like this:
self.to_field = to_field
in django.db.models.fields.related on ForeignKey init method.

comment:6 by Karen Tracey, 14 years ago

Resolution: fixed
Status: closedreopened

It's not fixed until patch is committed.

comment:7 by Karen Tracey, 14 years ago

Resolution: fixed
Status: reopenedclosed

(In [12756]) Fixed #11702: Catch to_field specifying a non-unique target in validation. Thanks marcosmoyano.

comment:8 by Jacob, 13 years ago

milestone: 1.2

Milestone 1.2 deleted

comment:9 by anandjeyahar1, 12 years ago

Easy pickings: unset
Severity: Normal
Type: Uncategorized
UI/UX: unset

Shouldn't this fix be specific based on the db being used? i.e syncdb should check the current db being used and raise an error only for postgresql or oracle. Am using mysql and i shouldn't be blocked from using a non_unique field as a foreign key.

comment:10 by Karen Tracey, 12 years ago

No. The validation is needed especially for databases that don't enforce this constraint. Django's ForeignKey is many-to-one, the Django code relies on that characteristic, and you can get odd results if the database does not enforce it, see for example this thread:!searchin/django-users/QuerySet.count%28%29$20inaccurate$20across$20ForeignKey$20relationships/django-users/fMmWVDr0Re8/overview

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