-
Notifications
You must be signed in to change notification settings - Fork 257
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
Support for Subquery and other expressions in annotate() #728
Comments
Hi, the only workaround is to use translated field name instead of generic name. But, you can look at the source code and try to add this feature. I'll gladly review and merge it. |
Sure I'll add it @last-partizan. can you just direct me to where i should focus on so I can add it? thank you. |
@celyes start by adding a test-case, and then - look at the |
Thank you |
Could you please share the test code that is causing the error? I would like to help resolve this issue as well. |
Thank you for this awesome package.
The plugin works perfectly for our needs except, however, when used with the
annotate()
where the annotate contains a Subquery expression or an F expression, it doesn't use the current language. For example, if the Subquery asks for a field called 'title', it's supposed to querytitle_en
ortitle_fr
or whatever is the current language but instead, it raises this exception:Once specifying the output_field, we get this exception:
Any idea how to work around this issue?
The text was updated successfully, but these errors were encountered: