similar to: ActiveRecord and tiny_tds

Hello Dear experts, I am new to Ruby on Rails. Though I want to access to MSSQL 2005 from ruby. I installed tiny_tds using following commands: >sudo apt-get install freetds-dev >gem install tiny_tds And now when I executed @client = TinyTds::Client.new( :username => ''username'', :password => ''password'', :host =>

Hi, I am trying to install the ruby-odbc gem on windows 2008 server Enterprise SP2 64 bit version I have installed the devkit for ruby and it is also getting installed. When trying to install this ruby-odbc gem some how make.exe file is getting crashing and I am unable to install it further. I am able to install the same gem on a 32 bit machine but the same procedure does not work out on 64

I would like to know if there is a way to ''package'' an application with all the associated gems and ship it to a new server and having it to "just work" in a Windows environment. Although I have never done it I know that Rails can be frozen into the application. I am wondering if I can do the same thing with other gems. I have found this

Not getting any love (tender or otherwise) on my pull request<https://github.com/rails/rails/pull/7035>so I thought you folks might like to chip in. What do you think? #cast and #cast! allow you to declare a mapping from generated column names to simplified database column types (i.e. those used in migrations). This way scopes with columns generated in their select lists can also include

I could not find the answer to this in a few Google searches and thought I would ask. So when are prepared statements best leveraged in ActiveRecord''s interface? I never really noticed before, but simple condition hashes or scopes do not pass down the binds so that prepared statements are leveraged. So a `Car.find(1)` would but things like `Car.where(:id => 1).first` do not. Is it a

Hi, today I went into a problem, when I had to iterate over a big result set. ActiveRecord produces a huge array of model instances, which consumed 1GB of memory on my machine. A comparable perl DBI script only used some KB for iterating over the result set. Then I was suggested to use batch (#find_each) for the problem. But basically batch does the same thing by splitting the query into several