Ahh. I suppose that makes sense. Is there any reason it doesn't show them by default?
On Nov 17, 3:45 pm, "Alex Koshelev" <[EMAIL PROTECTED]> wrote: > Try to use `--traceback` switch that prints exception's traceback > > On Tue, Nov 18, 2008 at 00:41, David Cramer <[EMAIL PROTECTED]> wrote: > > > I've been trying to dump some data to fixtures for the last couple > > days, and I've ran into various problems each time. It's been quite > > difficult each time to determine the problems, as there's no useful > > tracebacks on the error messages: > > > [EMAIL PROTECTED]:~/Development/iplatform] ./manage.py dumpdata > > businesses > data > > Error: Unable to serialize database: Category matching query does not > > exist. > > > While this is great and all (it beats the "recursive error" that > > appeared in previous revisions with the same models), it would be much > > more useful if some of the commands would give more detailed > > information so that you can actually diagnose problems :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
