Re: [Django] #22342: Changing a model to an abstract model caused "ValueError: Related model 'app.Model' cannot be resolved"

[Django]

#22342: Changing a model to an abstract model caused "ValueError: Related model
'app.Model' cannot be resolved"
+--
 Reporter:  blueyed |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:  worksforme
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by blueyed):

 Thanks for looking into this.

 I have came across a code comment, where I've linked to this ticket, but
 the code itself changed quite a lot already.

 IIRC your basic test case was what I was doing.

 Feel free to close this ticket because of lacking information, and because
 it has been fixed in the meantime already or was specific to some certain
 local-only change at that time.

-- 
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.3734b4db25c4a587fb5f1964a1b456f3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22342: Changing a model to an abstract model caused "ValueError: Related model 'app.Model' cannot be resolved"

[Django]

#22342: Changing a model to an abstract model caused "ValueError: Related model
'app.Model' cannot be resolved"
+--
 Reporter:  blueyed |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:  worksforme
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by bmispelon):

 * status:  new => closed
 * needs_docs:   => 0
 * resolution:   => worksforme
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 Hi,

 I can't seem to be able to reproduce this.

 I've tried creating a (non-abstract) model, running `makemigrations` and
 `migrate`, then changing the model to have `abstract=True` and running
 `makemigrations` and `migrate` again.

 When I do that, I don't get the error you mention.

 Could you provide us with the models you used (or better yet, a simplified
 version that still reproduces the issue)?

 Thanks.

-- 
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.e39fa604b068b5ea6b969c7eec054188%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.