When I ran:
./manage.py dumpdata --indent=2 databases > apps/databases/
initial_data.json
The dump loaded just fine into a new DB (it also works with no
indent). For some reason, I am now unable to reproduce the original
error, even though I'm following exactly the same steps that I
followed when I got the bad data. Looking at the JSON documentation,
it seems like I would be getting that kind of an error if I had
something like this:
[
{ <-- Note the extra curly bracket!
{
"pk": "3",
"model": "databases.subject",
"fields": {
"slug": "boom",
"title": "Boom"
}
}
} <-- End extra curly bracket
]
But that's certainly not what the output of the dump was.
In any case, I've closed the ticket as "worksforme". I'll reopen it if
I can ever reproduce it reliably.
Thanks for looking into this!
-Tyson
On Apr 12, 5:46 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> The error you mention suggests a syntax error in your file - the fact
> that the problem is on line 2 when all the data is on one line
> suggests that something in your file might be corrupted. I don't know
> how this would happen, though. To help track this down, can you run:
>
> ./manage.py dumpdata --indent=2 databases
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [EMAIL PROTECTED]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
