-
Notifications
You must be signed in to change notification settings - Fork 62
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
Casting to sa.Float (and some other types) silently does nothing #151
Comments
Hello @DelongChenQC Thank you. |
nothing ibmdb#151 Signed-off-by: Balram Choudhary <[email protected]>
Hello @DelongChenQC Fix for this issue is given with PR - #154 Thank you |
#154) nothing #151 Signed-off-by: Balram Choudhary <[email protected]>
Hello @DelongChenQC Fix for this with PR - #154 is merged now. Thank you. |
Thanks very much, sorry for the late answer, but LGTM 😄 |
When explicitly using the cast function to cast something into a sa.Float, the engine silently ignores this command and instead does nothing. This is especially dangerous when working with bind parameters as the implicit casting, does not work.
E.g:
When now executing this query, one would expect a float outcome, however due to the way the
python-ibmdbsa/ibm_db_sa/base.py
Line 450 in fdb3618
What is the reasoning for only having a set number of types that casting is possible to?
The text was updated successfully, but these errors were encountered: