Linked by Thom Holwerda on Fri 19th Jan 2007 16:16 UTC, submitted by Pieter Steyn
General Development "Rails 1.2 is finally available in all it's glory. We got the RESTful flavor with new encouragement for resource-oriented architectures. We're taking mime types, HTTP status codes, and multiple representations of the same resource serious. And of course there's the international pizzazz of multibyte-safe UTF-8 wrangling."
Thread beginning with comment 203568
To read all comments associated with this story, please click here.
Rails + Prototype
by robinh on Fri 19th Jan 2007 20:18 UTC
robinh
Member since:
2006-12-19

Seems to me the the Rails javascript 'spinoff' prototype is making more of an impact than Rails itself, which is interesting given that some of the features in prototype are designed to be ruby-esque. BTW... Does Ruby still use the 'Active record' DB mapping model? I remember looking at this stuff before and thinking that it's probably not suitable for large scale or unusual projects?

Reply Score: 1

RE: Rails + Prototype
by openwookie on Fri 19th Jan 2007 20:45 in reply to "Rails + Prototype"
openwookie Member since:
2006-04-25

Does Ruby still use the 'Active record' DB mapping model? I remember looking at this stuff before and thinking that it's probably not suitable for large scale or unusual projects?

Yes, ActiveRecord is still in use.

Its fine for large scale and 'unusual' projects. If you need to call a stored proc, or run some sort of crazy table join, you can write custom code in your model to do that.

Also, if your schema does not conform to what ActiveRecord expects (ex: primary keys are not named 'id'), you can configure your model object so that ActiveRecord uses the correct fields.

Reply Parent Score: 1