This will probably be very helpful. Thanks.

On Wed, Feb 24, 2016 at 3:39 PM, James Schneider <[email protected]>
wrote:

>
>
> On Wed, Feb 24, 2016 at 11:26 AM, Malik Rumi <[email protected]>
> wrote:
>
>> I am pursuing the debug option now to see what I can learn.
>>
>>
>>
>
> Have you looked at enabling tracebacks (--traceback) and increasing the
> verbosity of the loaddata command (-v {0,1,2,3}, --verbosity {0,1,2,3})?
>
> $ python manage.py help loaddata
> usage: manage.py loaddata [-h] [--version] [-v {0,1,2,3}]
>                           [--settings SETTINGS] [--pythonpath PYTHONPATH]
>                           [--traceback] [--no-color] [--database DATABASE]
>                           [--app APP_LABEL] [--ignorenonexistent]
>                           fixture [fixture ...]
>
> Installs the named fixture(s) in the database.
>
> positional arguments:
>   fixture               Fixture labels.
>
> optional arguments:
>   -h, --help            show this help message and exit
>   --version             show program's version number and exit
>   -v {0,1,2,3}, --verbosity {0,1,2,3}
>                         Verbosity level; 0=minimal output, 1=normal output,
>                         2=verbose output, 3=very verbose output
>   --settings SETTINGS   The Python path to a settings module, e.g.
>                         "myproject.settings.main". If this isn't provided,
> the
>                         DJANGO_SETTINGS_MODULE environment variable will be
>                         used.
>   --pythonpath PYTHONPATH
>                         A directory to add to the Python path, e.g.
>                         "/home/djangoprojects/myproject".
>   --traceback           Raise on CommandError exceptions
>   --no-color            Don't colorize the command output.
>   --database DATABASE   Nominates a specific database to load fixtures
> into.
>                         Defaults to the "default" database.
>   --app APP_LABEL       Only look for fixtures in the specified app.
>   --ignorenonexistent, -i
>                         Ignores entries in the serialized data for fields
> that
>                         do not currently exist on the model.
>
>
> -James
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Django users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/django-users/Q4zybgExDyY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CA%2Be%2BciVUtK1LtfpfsNBRF1chO_wxG_pabr8F3wZRZVR6G0SwqQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/django-users/CA%2Be%2BciVUtK1LtfpfsNBRF1chO_wxG_pabr8F3wZRZVR6G0SwqQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAKd6oByayoyiXFBTUFKPcD%3DKXp0PDVNx1XkyUps7E%2B9UBoiEUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to