These are chat archives for rails-sqlserver/activerecord-sqlserver-adapter

13th
Aug 2015
Michael Lang
@mwlang
Aug 13 2015 00:38
Starting a new Rails 4.2 project today, but unfortunately hitting a MSSQL 2005 server. Is it possible to use the 4-1-stable branch on Rails 4.2 or is that a complete non-starter?
Ken Collins
@metaskills
Aug 13 2015 10:29
@mwlang That is non-starter. rails-sqlserver/activerecord-sqlserver-adapter#406
Michael Lang
@mwlang
Aug 13 2015 13:58
That's what I thought. I've been digging into the two different code branches after asking my question.
I'd update the README slightly to make the point more clear. This sentence: "Just install the latest 3.2.x to 4.1.x version of the adapter. " wasn't entirely clear that one couldn't just use the 4.1.x version of the adapter with Rails 4.2 even with the additional note about rational versioning.
Michael Lang
@mwlang
Aug 13 2015 14:05
So how about changing that to "Your projects will need to use Rails 3.2.x or 4.1.x which corresponds to the 3-2-stable and 4-1-stable branches of the adapter. "
as it is, it sounds like all you gotta do is downgrade your adapter in your Gemfile and you're good to go.
Ken Collins
@metaskills
Aug 13 2015 19:17
@mwlang Yea… why did the point of rational versioning policy coupled to ActiveRecord not make that clear for you?
We follow a rational versioning policy that tracks ActiveRecord. That means that our 4.2.x version of the adapter is only for the latest 4.2 version of Rails.
Maybe that should go first in the paragraph after the intro line?
Michael Lang
@mwlang
Aug 13 2015 21:41
@metaskills Well that sentence says it tracks "ActiveRecord" not "Rails" so the door was still open to thinking "maybe 4.1-stable will work on 4.2 Rails" -- that's the uninitiated point of view, but I see the fault in that now.
also, "4.2.x version is only for the latest 4.2 version of Rails" makes perfect sense as stated -- that tells me I can't use the 4.2.x version on earlier versions of Rails but doesn't rule out that 4.1.x version doesn't work on 4.2 version of Rails.
hindsight, of course, is 20/20 and "just trying it" showed it wouldn't work.