If you are using Rails why would you want to do that? Rails performs
a lot of its magic by having default rules that allow it to work out
what you want without you having to tell it all the details. For
example, if you want to handle comments then the model class is
Comment, the table name is comments, the controller is
CommentsController, etc. It is possible to override all these but if
you want to get the maximum out of Rails then don't, unless you have a
specific problem that you need to address.
When replying please quote the previous message so that we can see
what you are replying to. This is a mailing list not a forum, though
you may be accessing it via a forum like interface. Thanks.
Have you asked why he/she wants to do that?
As far as I know you can just use, in the migration,
create_table :ANYNAMEYOULIKE
but I have not tried it.
Maybe, table name aliasing might come in handy. The main problem that I foresee is that when migrating from mysql to some other, you have to be conscious about the aliases. The same holds true when you are creating a table. But then, rails migration dsl might provide you with a consistent way of doing this.
Hope this helps.