#3233: manage.py reset fails to handle valid sql file
---------------------------------------+------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: Tools
Version: 0.95 | Resolution:
Keywords: [EMAIL PROTECTED] | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------------------+------------------------------------
Comment (by Marc Fargas <[EMAIL PROTECTED]>):
It's possible that the max_allowed_packet for MySQLdb is not enough to
load your file while the one for the mysql client is larger enough. This
setting has to be enough on the server and the client and manage.py reset
uses the python mysql module to load your file, while manage.py dbshell
drop you into the mysql client itself.
I tried to read about that on the MySQLdb site but it's down so I cannot
confirm that. But it's a possibility. Another possible cause is the way
manage.py reset sends the file to the server and how the mysql client does
(maybe one splits the file into statements and the other sends the file as
a whole?)
Just some ideas on where could the problem be.
--
Ticket URL: <http://code.djangoproject.com/ticket/3233#comment:6>
Django Code <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 [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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
