On Wed, 2009-07-29 at 22:20 +0200, Marnen Laibow-Koser wrote: > Craig White wrote: > [...] > > thanks - I have used Rails quite a bit but have always used ez-where > > (Rails 1.1/1.2) and it made it easy for me to do finds. > > I'm not familiar with ez-where, but it sounds like it's made it possible > for you to do lots of things without understanding the underlying SQL. > That may not be a good thing: automation is great, but you should always > understand what's being automated -- use it as a tool, not a crutch. > > > > > It simply doesn't work in Rails 2.3.2 and thus it has forced me into > > executing finds using Rails code directly which is not where I want to > > spend so many hours. > > Spend 30 minutes with your database's SQL docs and another 15 minutes > with the ActiveRecord rdoc, and all will be come clear. It's not > particularly difficult, but it is essential. ---- I'm not disagreeing with you but I am furiously trying to do some reports from mysql legacy database system when I am familiar with Rails 1.2 and postgresql and ez-where. I think if you had been spoiled by a tool like ez-where, you would understand why I was so lost without it. I never really had to construct SQL queries...at least not beyond simple.
Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
