My experience would be to recommend AR first. Especially if you're going to try to use testing tools like Cucumber and such. They are all geared toward AR first, then maybe DataMapper or Mongo. Sequel require you to do some message board posting/searching (which Jeremy diligently responds to) but ultimately everything can work if you're willing to put in a little more effort. I have a legacy DB with custom SQL that I found a lot easier to implement in Sequel. I like the ability to create SQL queries using the nice Sequel API and then tack on my own custom stuff. That is a lot harder to do in AR.
Jason On Feb 25, 3:37 pm, Kedar Mhaswade <[email protected]> wrote: > I have been teaching Ruby and Ruby on Rails to myself. I ran into > geonames processing and then came to know of Sequel and it looks cool. > Some search also reveals that it has very good performance > characteristics. But then I am unsure of whether I should learn/use > Sequel instead of activerecord for my first RoR web application. The > Web is full of tutorials, advice regarding AR, (ar-extensions too), > but not about Sequel. > > For a relative newcomer to Ruby/RoR how'd you advise regarding using > Sequel? Should I learn it or make sure I am through with AR, > migrations, associations, finders and then come to Sequel land? > > Thanks in advance, > Kedar -- You received this message because you are subscribed to the Google Groups "sequel-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/sequel-talk?hl=en.
