Querying failed if target table has datetime column on Windows

[yasuyuki]

Querying failed if target table has datetime column on Windows

[metaskills]

I think you are hitting of of those odd 32 bit bugs on Windows only for certain DateTime objects that are out of bounds for that ruby version. This is an old throwback bug to Ruby in general on Windows. Have you tried using TinyTDS 0.5.0 release candidate yet? Also, I would update Ruby too if you have the option.

[yasuyuki]

I tried 0.5.0.rc1. It works fine. Thank you.

[jackross]

I also ran into this same problem with a datetime column, however I am on 1.9.2-p290 on Snow Leopard (not Windows) with the latest gem (0.4.5). Using the 0.5.0.rc1 fixed it for me too. Thanks for the suggestion, metaskills and the feedback, yasuyuki, and Thanks! meta for a great gem!

[gardwired]

hi, i am running into this same issue on debian linux ruby 1.8.7p320, tiny_tds 0.5.0 and freetds 0.91 qyering against windows 2000/sqlserver 2000 virtual machine (vmware). ie ruby is all on linux. i was getting these "statement invalid...argument out of range" errors on any query that has a datetime field (so almost all of my queries fail because of updated_at/created_at). this is a real show stopper. am really wanting to dump odbc. other details are that i compiled freetds without odbc, default tds 7.1 and enabling ms libs. the install all seemed to go fine (debian lenny doesnt have freetds 0.91 as yet).

i was getting the errors in rails 2.3.14 console so i then tried using TinyTds.client directly. same issue (argument out of range) when i try to iterate through result. fine if i dont select datetime fields.

please advise. am willing to help debug if needed. again, this doesn't appear to me to be a windows issue as these queries run fine on mssql query analyzer. it is only when you try to actually read the field in tds (convert string to Time?) that i pukes. i am not (and would prefer not to) use /etc/freetds/freetds.conf unless i have to to get this to work.

any ideas?