Skip to content
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

SQL Server 2000 #50

Closed
hughevans opened this issue Aug 16, 2010 · 5 comments
Closed

SQL Server 2000 #50

hughevans opened this issue Aug 16, 2010 · 5 comments

Comments

@hughevans
Copy link

Do you think it's much work to support it again with Rails3?

@metaskills
Copy link
Contributor

Hard to say, but I get the feeling it would be a pain. We were able to remove so much string operation code due to the crazy things we needed to do to the SQL to get test to pass. At a top level it looks simple, come up with a taken/offset alternative. But in actuality it is very much more difficult than that. Things like association limiting and the myriad of conditions, join, etc that can affect the validity of the SQL make it so much more difficult.

This patch is going to have to come from the field or another contributor if they feel the pain enough. I too am on SQL Server 2000 and we are going to just upgrade when needed. But if someone wants to write the code, I will take a look at tested patches.

@demersus
Copy link

SQL Server 2000 support would be very helpful. I have a huge application running at my organization that is half ASP.NET and half Rails. Unfortunately upgrading the database is not an option until I can rewrite all of the old ASP.NET stuff in Rails. I would like to use Rails 3 for continued development, but I see that I cannot because of no mssql server 2000 support..... I appreciate all of your work so far, thank you. It has helped me to start migrating to Rails.

@metaskills
Copy link
Contributor

Thank you, but this patch will have to come from the field. I too am In the same boat. But we are going to upgrade SQL Server sometime before moving to rails 3. My efforts are on more important things and I'll need to see a patch come from the user base vs taking this on on my own. It will not be easy and I'm almost certain anyone that tires to hack this up working for the arel compiler will end up failing and still failing most of the tests. Honestly it is not easy. So when someone feels the pain, I will apply a tested patch.

@demersus
Copy link

mssql server 2000 is 10 years old anyway. I completely understand dropping support for it. It always feels like I have to jump through so many hoops to get MS technology to work for me. This will help me pitch my conversion strategy.

@metaskills
Copy link
Contributor

Yea, rails 3 getting 2000 support is not really going to happen since, if something comes from the field, I will look at it.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants