Re: [Django] #29466: Textual "to" parameter of ForeignKey fails to resolve if placed in abstract model

[Django]

#29466: Textual "to" parameter of ForeignKey fails to resolve if placed in 
abstract
model
-+-
 Reporter:  Vitalik Verhovodov   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Vitalik Verhovodov):

 Sound reasonable, but what if I'm sure that all models are already loaded
 (e.g. during Command execution)? How can I manually resolve textual model
 name and target_field?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.9d4638f8e73eebca3a0066aa518471d7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29466: Textual "to" parameter of ForeignKey fails to resolve if placed in abstract model

[Django]

#29466: Textual "to" parameter of ForeignKey fails to resolve if placed in 
abstract
model
-+-
 Reporter:  Vitalik Verhovodov   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Alexander Tatarinov):

 I will assume that this is intended behavior. According to #24215,
 abstract models does not register pending lookups into Apps registry. I
 have tried to implement it, but found an issue with recursive relations in
 abstract model - they cannot be resolved but it is valid to have them,
 because they can be resolved in concrete children classes. So for abstract
 models lazy-referenced relations should not be resolved. I would not
 change the triage stage as I am not sure about this.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.2b17ee27684ca08e7811c473d4c24a2f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29466: Textual "to" parameter of ForeignKey fails to resolve if placed in abstract model

[Django]

#29466: Textual "to" parameter of ForeignKey fails to resolve if placed in 
abstract
model
-+-
 Reporter:  Vitalik Verhovodov   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * stage:  Unreviewed => Accepted


Comment:

 Reproduced at 741792961815cf4a95c5ce8ab590dfc7700c6153.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.bc14fa15373b6a29841398ae1d2493ec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.