-
Notifications
You must be signed in to change notification settings - Fork 128
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
Accessing stored fields on proxy models fails #160
Comments
I'm afraid I'm away at the moment, but will have a look when I'm back next On Thu, 7 Apr 2016 at 20:03 Ryan Rubin [email protected] wrote:
|
Okay, it looks like django-watson doesn't support separate registration for proxy models. I guess it probably should. There are a few changes that are needed:
I'll take a pull request that implements this, if it's urgent. |
I'm running django-watson 1.2.1 with django 1.8.12. I have a model setup that involves a few proxies for different product types which are all stored on the same
Product
table. I've registered the proxies separately with watson:This works fine for most things, except when I try to access any stored fields, when it tries to deserialize the
meta
based on the root model, not based on the proxy, and throws an error because that root model is not registered with Watson:Now, the problem is solved if I register an empty queryset from the Product model so that it knows how to deserialize the meta, but that doesn't seem like an ideal solution:
The text was updated successfully, but these errors were encountered: