I need some advice. I am in a position at work where I’ve got the boss
pretty excited about rails. I think I could swing the Next Generation
version of our product to use rails as the platform, but I find myself a
little hesitant to do so until I’ve answered a few issues that I’m
people on this list could help me with.
Firstly, we are tied to SQLServer 2000. Our application contains a lot
stored procedures and triggers and a legacy table structure. So for
we have always and are always likely to run on Windows.
Is Rails on SQLServer ready for the prime time?
Have the issues with primary key names been resolved (Used to need to
your key id or otherwise always include an explicit :order_by)?
Do transactions work properly (the SQLServer DBI code “looks” like it
each command in a transaction - I’ve had rake unable to do unit tests
because it couldn’t set up the fixtures due to the connection already
in a transaction)?
Do migrations work? I’ve heard yes, but haven’t had the opportunity to
Is performance acceptable? Is there much overhead in the SQLServer
adapter? (I wouldn’t imagine so, but…).
Can ActiveRecord map a legacy database structure acceptably?
Can I work direct-db calls and ActiveRecord code? We have many
informational queries and stored procedures that we will work with that
not map to objects.
Do triggers cause problems for ActiveRecord (I’ve seen suggestions
this might be the case on this list)?
Do the unit and functional tests work properly for SQLServer?
For any issues above - is there any work being done to address them?
I would dearly love to be able to use Rails for this project. It has so
compelling advantages over other alternatives (currently ASP.Net using
Delphi, or PHP) but the issues we may face with SQLServer are a concern.
am working on implementing a part of our system in Rails as a
proof-of-concept and would appreciate any help that this list could
to make this process faster and easier.