#24853: FK value not inserted in database in data migration
-------------------------------------+-------------------------------------
Reporter: rakanalh | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 1.7
(models, ORM) |
Severity: Normal | Resolution:
Keywords: database, | Triage Stage:
migrations | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by shaib):
* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0
Comment:
Hello,
Thanks for taking the trouble to submit this problem report. Some points
arise:
1) Per Django's maintenance policy, only major bugs (security issues or
data-loss problems) will be fixed in 1.7. Can you please try to reproduce
the issue with the current 1.8 release?
2) While you're at it, if the problem still exists, and to help pinpoint
it, please try to replace the line
{{{
scraped_obj_attr.obj_class_id = scraped_obj_class.id
}}}
with
{{{
scraped_obj_attr.obj_class = scraped_obj_class
}}}
In principle, it should be equivalent.
3) Could you please clarify how you dealt with django-dynamic-scraper's
migrations? The current source has a migrations folder, but those are
South migrations, incompatible with Django>=1.7.
Thanks,
Shai.
--
Ticket URL: <https://code.djangoproject.com/ticket/24853#comment:1>
Django <https://code.djangoproject.com/>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.1b3bd724d73e6713ee1cc7db1405c7b2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
