David Zhu wrote in post #971909: > Which is better? And why? David: I certainly defer to the wise words of Marnen, Phoenix and Colin.
One case where you might want to split one logical entity into two tables is when you have a "transaction" part (frequently changing) and a "static" part (rarely changing). To state the obvious, if you wanted to capture login times and IP addresses for your users, that would certainly be a table separate from the rest of the user information. If you're keen to learn more philosophy about database design, try a google of "Dimensional Database" and/or "Ralph Kimball". But beyond that, yeah, one table should suffice for your needs. - ff -- Posted via http://www.ruby-forum.com/. -- 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.
