On Tuesday, January 7, 2014 8:52:30 PM UTC-8, Ross Attrill wrote: > > The 4.1 release notes contain this comment: > > > > > > *"The :driver option to the odbc adapter is deprecated and will be > removed in a future version. It is thought to be broken, and users > wanting to use DSN-less connections should use the new :drvconnect > option."* > > And the code in here: > > > https://github.com/jeremyevans/sequel/blob/master/lib/sequel/adapters/odbc.rb > > > this: > > Deprecation.deprecate("The odbc driver's handling of the :driver option > is thought to be broken and will probably be removed in the future. If you > are successfully using it, please contact the developers.") > > My experience using > * ruby-odbc 0.99995 > * sequel 4.5.0 > * :driver=>'SQL Server Native Client 10.0' > > Is that the :driver option does work. > > My full connection string is like this: > > DB = Sequel.connect(:adapter=>'odbc',:driver=>'SQL Server Native Client > 10.0',:server=>'localhost',:port=>1433, > :uid=>'exl',:pwd=>'mypass',:db_type=>'mssql') > > I can get the newer :drvconnect approach to work as well (and thus avoid > deprecation messages), however given that :driver is working in the above > context I wonder if it is beneficial or not to deprecate - or perhaps > deprecate in the contexts where it doesn't work. > > Thank you, > > Ross Attrill. >
Ross, Thanks for the feedback. Now that I know it can be used successfully, I've removed the deprecation warning. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/groups/opt_out.
