Thanks for the input, Rick and Fred.
> comments is pluralized because a post has many comments (1:n
> association)
>
> post is singular because a comment belongs to a single post, not
> several.
OK. From a grammatical perspective that certainly makes a lot of
sense. However, it sure messes with my mind from a programming
perspective. Personally, I'd much prefer to be able to refer to
something pretty much as I defined it and not have to worry about what
is going to be altered and what isn't. I understand that with Ruby
there is going to have to be some flexibility in that regard because
of Ruby naming rules such as, "constants must begin with a capital
letter".
Please correct me if I'm wrong; but, this is an ActiveRecord issue,
not a pure Rails issue, right?
Is there anyway that I can turn off the pluralization behavior? That
would go a long way towards retaining order in my life.
As far as the camelcase and underscore thing goes, how about I just
define my model classes to be 'Blog_post' and 'Blog_comment'
respectively? Then, with the pluralization turned off (if that's
possible),
the only variation that I would have to worry about relates to the
case of the initial letter. Dealing with that should be pretty easy
because it just requires that one follow the Ruby naming rules. What
do you think?
... doug
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
