-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Example data errors #3
Comments
Are you using django-south? |
django-south is installed in my virtualenv, but I've yet to install it within my django application (but will soon). |
Could you post a full stacktrace? |
[04/Dec/2012 19:04:40] "GET /api/v1/support-ticket/schema/ HTTP/1.1" 200 2182 |
mmmh Maybe there's an issue when south is installed on the python env but not as a django auth? |
Jackpot. Strange error since south isn't even installed... Your suggestion took care of the 'migrations' error, but then I received: Exception at /docs/example/support-ticket/ I verified that if I delete the referenced uuid field on the SupportTicket model then everything works like a charm. |
That happens when django-chocolate cannot create a value for |
UUIDField from the django-extensions app: https://github.com/django-extensions/django-extensions |
Yeah, the solution for that is provide your own mock generator for that value. That feature is well supported on django-chocolate (the lib used by django-tastydocs to generate the examples) but I'm not sure if it's well integrated with tastytocs. I'll try to take a look at that during the week. You can always try to poke around it by yourself. |
Yeah I'll definitely take a look myself. Thanks for the timely responses and the work you've put in on this. |
When trying to view /docs/example/<resource_name>/ I receive a DatabaseError:
no such table: tastypie_apikey
... in the browser.
I am generating api_key objects in a receiver function for the 'post_save.connect' signal on the 'auth_models.User' model. If I disable the receiver connection, I receive:
Error: Unknown command: 'migrate'
followed by a 500 error notification in the terminal.
The text was updated successfully, but these errors were encountered: