-
Notifications
You must be signed in to change notification settings - Fork 308
Fix with_alias argument in terms classes #616
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
Comments
I ran into the same problem. And sadly this great package seems to have gone quiet, so I'm guessing no changes are going to get pulled in. Thus, I fixed it for myself. I tested it out, albeit lightly, and it seems to be working in that the alias is still present for the SELECT clauses, but removed in the WHERE clauses. Maybe it'll help you. |
see #735 |
Hello, I inherited this package and will now take care of it. Thank you for raising the issues and finding solutions to them |
Hi, I noticed that some terms do not use the
with_alias
parameter in theget_sql()
function always returning the sql string formatted with alias even if thewith_alias
parameter is set to false. I was wondering if there is a reason to have some terms with this behavior or if the logic is missing in some terms.The problem is that if the alias is used in the
WHERE
clause of a SQL query it breaksFor example the
get_sql()
function of the term classNullCriterion(Criterion)
is defined as follows:Shouldn't be more correct to have:
The same applies for other terms like
BetweenCriterion
,BitwiseAndCriterion
,NullCriterion
and othersThe text was updated successfully, but these errors were encountered: