-
Notifications
You must be signed in to change notification settings - Fork 20
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
Columns reference can be ambigous #26
Comments
There is alpha branch, I think it should be fixed there. |
It has more changes than you can see in master. But they all relates to sql generation not to ORM integrations so very likely ORM parts should be adjusted |
Yeah, I saw the alpha branch, I've made the last tests with that. This issue and #25 refer to the BTW: Thank you for your work on casl, it's really awesome! 😃 |
ccatterina
pushed a commit
to ccatterina/ucast
that referenced
this issue
Aug 26, 2022
Fix issue stalniy#26 for TypeORM adapter
ccatterina
pushed a commit
to ccatterina/ucast
that referenced
this issue
Aug 26, 2022
Fix issue stalniy#26 for TypeORM adapter
ccatterina
added a commit
to ccatterina/ucast
that referenced
this issue
Aug 26, 2022
Fix issue stalniy#26 for TypeORM adapter
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Interpreter can translate a condition in a SQL Query with ambigous column names. This can happen when the condition is based on both a related table fields and the main table fields.
A solution could be to prefix all the fields in the where condition with the main table alias. What do you think about it?
The text was updated successfully, but these errors were encountered: