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
Haven't had a chance to check/test but detule@e833f18 should, in theory address this. It moves the the "fix" to a location where it should hopefully get picked up for SELECTs that are prepared (in addition to those that get executed immediately).
Will take a closer look next week unless someone beats me to it.
Thank you thank you thank you thank you thank you thank you thank you thank you!
Celebratory music, confetti cannons, crowds screaming, gaiety abound. Christmas and Kwanzaa come early with this commit, and though it may be a few days late for Chanukah, I think celebration will still be had by many.
(If it isn't obvious by now, I'm very grateful for your efforts, individually and collectively. Thanks @detule, @jimhester, @krlmlr, and all others who are a part of this. Happy Holidays, everybody!)
Issue Description and Expected Result
This is a continuation of #358, #309, and several others.
The recent fixes seem to work well with "regular" text, but when we introduce bound parameters, it fails.
Database
SQL Server 2017, running on docker. Versions:
Reproducible Example
SFSG. If we use bind-params without column-order being a factor, it works:
But the same query with the column-order issue fails:
Session Info
This is with the CRAN release of
odbc
, but I also just installed the github version 1.3.0.9000 and get the same results.The text was updated successfully, but these errors were encountered: