#1661 closed defect (fixed)
Forward declaration of OneToOneField requires 'to_field' to avoid import failure — at Version 1
| Reported by: | Russell Keith-Magee | Owned by: | Russell Keith-Magee |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | magic-removal |
| Severity: | normal | Keywords: | |
| Cc: | lists@… | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
njharman (lists@…) reports:
class Foo(models.Model):
myfield = models.OneToOneField('SomeModel', to_field='id')
Works.
class Foo(models.Model):
myfield = models.OneToOneField('SomeModel')
Fails because whatever "turns" 'SomeModel' from string into class object
hasn't happened when code in
"/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/db/models/fields/related.py
on line 510 tries to determine default to_field.
Model is ok during syncdb; failure occurs during import.
Change History (1)
comment:1 by , 18 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
(In #3197) Fixed #1661 -- Added logic for string-form model references in the 'to' argument of OneToOneFields?. Includes regression test.