That kind of thing should never ever be done. Imagine when you reach, maybe, a thousand users, you'll have at least thousand tables! Then imagine when you need to make a change in the users' tables! I strongly recommend to make use of Rails' has_many and belongs_to associations to keep track of which records belongs to which users, instead.
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Can (should) each :user have his own table? | 8 | 159 | October 20, 2009 | |
Creating Tables at RUNTIME. | 6 | 94 | March 17, 2008 | |
One huge table or separate tables? design issue | 15 | 469 | November 4, 2014 | |
Best way to handle multiple tables to replace one big table? | 15 | 1219 | April 30, 2010 | |
Database/program design question | 6 | 118 | January 9, 2008 |