-
Notifications
You must be signed in to change notification settings - Fork 191
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
Added separate user projection in query help for rest api #2793
Conversation
aiida/restapi/translator/node.py
Outdated
@@ -268,7 +269,7 @@ def _get_content(self): | |||
return {} | |||
|
|||
# otherwise ... | |||
node = self.qbobj.first()[0] | |||
node = self.qbobj.all()[0][1] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should see with Leonid why this is not possible anymore.
If we don't find a solution, a ticket should be opened.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be merged after it is tested with the django_jsonb branch where the hybrid properties are removed. I will need help from @sphuber to rebase the django_jsonb branch since after his last PRs I have conflicts that are not obvious to resolve. Then we can test this PR with the rebased django_jsonb and merge it to develop. |
I have tested this with the |
Automatically projection user email for nodes relied on hybrid properties in SqlAlchemy, which have been removed. The alternative is to explicitly join on the User entity and project separately.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @waychal
Resolves #2764