#12007: djangoadmin loaddata gives odd error if it runs out of memory
------------------------------------+---------------------------------------
Reporter: chrisw | Owner: nobody
Status: new | Milestone:
Component: Serialization | Version: 1.1
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by russellm):
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* component: Uncategorized => Serialization
* needs_tests: => 0
* needs_docs: => 0
Comment:
For those looking to dig into this, it's important to identify whether
this is a database issue (i.e., the database runs out of memory if you try
to do a 3GB transaction) or a Django issue (i.e., a problem with our
wrapper loading the data file into memory).
Its also important to note the analog with #5423 - that ticket deals with
making dumpdata behave as an iterator. I'm not marking this as a dupe
because the solution won't necessarily be the same, but it's worth noting
if someone wants to tackle both problems.
--
Ticket URL: <http://code.djangoproject.com/ticket/12007#comment:1>
Django <http://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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
