-
Notifications
You must be signed in to change notification settings - Fork 558
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
Run tests in odbc mode #310
Comments
Hi Anna, I would prefer that we will drop the odbc mode, as the odbc code is, hmm, "difficult" |
ODBC is occasionally quite useful, so I won't be dropping it. I used it a few weeks ago for rmre (models reverse engineering). I finally got it set up on my machine and ran the tests and it wasn't that bad. Just a few encoding issues. https://gist.github.com/annaswims/c79c4c10fe951f2673ea |
Up to you, ODBC is slow and the ruby gem has no open presence since last I looked. It also did not do native Ruby data types conversions which added to the speed issue. IMHO, TinyTDS is so much faster and cleaner. There seems to be some great work being done on it too. |
I agree that TDS is the way forward and the obvious first choice, but considering that ODBC is (mostly) working I'd like to just leave it alone for now. I benefited greatly from ODBC in the past month when I used it for rmre (essentially a one-time script) and then switched right back to using TDS. |
Kewl, unless something that pops up that considerable takes it out of the running, I would just continue to document the tests that can not pass under ODBC. In the past, these were mostly date time cast issues. |
I haven't successfully set up odbc mode on my machine yet. If someone could run the tests in odbc mode I'd be grateful.
The text was updated successfully, but these errors were encountered: