This post originated from an RSS feed registered with .NET Buzz
by Brad Wilson.
Original Post: 10 Reasons Rails Does Pluralization
Feed Title: The .NET Guy
Feed URL: /error.aspx?aspxerrorpath=/dotnetguy/Rss.aspx
Feed Description: A personal blog about technology in general, .NET in specific, and when all else fails, the real world.
One thing in Ruby on Rails that always takes people by surprise is the pluralization engine.
For example, your database table named 'people' will be represented by a model object named 'Person' (to represent one row in the database). The Rails engine actually does all this automatically... creating the Person model automatically tells Rails that the table name will be 'people' (you can override this behavior if you don't like it, of course).
It is pretty unusual, and tends to spawn a moderately regular flame war on the Ruby or Rails mailing lists/news groups. In vein of humor, David posts his 10 Reasons Rails Does Pluralization.
(Brought to you during Advanced ASP.NET 2.0 training. <grin>)
Previous Topic
