You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SQLAlchemy has changed some of their function calls in newer versions which break SKompiler's SQLAlchemy methods. I did my testing with SQLAlchemy==2.0.21.
and get an output without errors, but the parameters are no longer replaced. The SQL output will be something like:
SELECT CASE WHEN ("Your Column Name Here"<= :param_1) THEN :param_2 ...
The from_obj parameter has been deprecated - along with all kwargs. After a quick look I don't see how to bring the values in from result.from_obj. This is also probably an issue with this sa.select()call in _make_cte().
There maybe other issues with the SQLAlchemy integration, these are just the two I found in my testing.
SQLAlchemy has changed some of their function calls in newer versions which break SKompiler's SQLAlchemy methods. I did my testing with
SQLAlchemy==2.0.21
.One simple fix is in the
_iif()
function return whereshould now be
as the
whens
parameter is now a series of tuple arguments, not a list.However, there is still an issue with the
sa.select()
calls. For example intranslate()
you can alter this line fromto
and get an output without errors, but the parameters are no longer replaced. The SQL output will be something like:
The
from_obj
parameter has been deprecated - along with all kwargs. After a quick look I don't see how to bring the values in fromresult.from_obj
. This is also probably an issue with thissa.select()
call in_make_cte()
.There maybe other issues with the SQLAlchemy integration, these are just the two I found in my testing.
CC @konstantint
The text was updated successfully, but these errors were encountered: