Hi all, I'm trying to import a JSON fixture using loaddata. It gives me a ProgrammingError because it seems that it's trying to put to much data in a varchar. Without access to the variables in that scope, I'm quite lost which record is causing this. Using "python -i manage.py loaddata --traceback" doesn't give me the opportunity to debug this using the pdb postmortem debugger because the --traceback option just prints the traceback to stdout.
In an older revision, this would just raise the exception. However, this behavior has been changed because raise always gives a TransactionError. So, should I open/reopen a ticket because --traceback was added to help with debugging? However, it is quite worthless in int's current state. For now I'm just catching all errors that the save call in the loaddata command generates and start pdb from there running set_trace. Are there other/better ways to raise the original exception instead of the TransactionError? Bram --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
