#20933: manage.py loaddata stopped working on Django 1.6b2
-------------------------------------+-------------------------------------
Reporter: static | Owner: aaugustin
Type: Bug | Status: assigned
Component: Database layer | Version:
(models, ORM) | 1.6-beta-1
Severity: Release blocker | 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 apollo13):
Replying to [comment:3 aaugustin]:
> Right. I must have broken loading fixtures from an absolute path — the
third option mentioned here: https://docs.djangoproject.com/en/dev/howto
/initial-data/#where-django-finds-fixture-files
No, absolute paths work as intended:
{{{
./manage.py loaddata `pwd`/appname/fixtures/groups
Installed 3 object(s) from 1 fixture(s)
}}}
The issue is relative paths, which aren't documented to work, though it
would make sense that they do, I'll see what I can do.
--
Ticket URL: <https://code.djangoproject.com/ticket/20933#comment:7>
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/064.1f0b84e97913d0923eea3d3a26121532%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
