-
Notifications
You must be signed in to change notification settings - Fork 129
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
Problem with watson during loaddata command call #250
Comments
I suggest to check if |
Sounds sensible, although it would require running a manual buildwatson
command after using loaddata.
I'd take a pull request for this.
…On 11 September 2018 at 20:45, Gabriel de Biasi ***@***.***> wrote:
I suggest to check if raw=False when catching the post_save signal in
order to ignore actions made in loaddata call.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#250 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJFCAbMrcbXT8W9HtYgBU2azH3HRu9Dks5uaBL1gaJpZM4WkF8Z>
.
|
I will appreciate this.
|
I made a workaround for this, using an environment variable. And in
After that, I call |
One of my models has "db-related" url. When I call
get_absolute_url
will hit the database.When I use loaddata to load a dump of my app, watson already tries to use the object and hit the
get_absolute_url
method, resulting in a "matching query does not exist" and stop all the process.Is there a way to tell watson to not try anything during a loaddata call?
Resulting trace:
The text was updated successfully, but these errors were encountered: