And if your database gets over 5,000,000,000 records give yourself a high-five for a job well done! I think David Zentgraf's suggestion for the table is a much better / normalized system. In your suggested system how do you query a users records for all years they have been using the application? How do you get every users' data for every feburary? Dynamically making tables and models is not the best solution in most cases that I've come across.
-Mark On Sep 4, 10:39 am, "David C. Zentgraf" <[EMAIL PROTECTED]> wrote: > Dude, don't worry about non-issues... :-D > > Scalability and Limits: > • Handles large databases. We use MySQL Server with databases that > contain 50 million records. We also know of users who use MySQL Server > with 60,000 tables and about 5,000,000,000 rows. > > http://dev.mysql.com/doc/refman/5.1/en/features.html > > On 4 Sep 2008, at 23:31, Wole wrote: > > > > > Thanks for all the help guys. My concern with keeping everything in > > one table is that the table has the potential of getting very large, > > which could affect performance. Supposing I have 500 users this means > > the table would grow by 500 entries each year. I know MySQL can handle > > large tables but I'm not sure of the limitations. Maybe I'll try the > > one table approach then switch to multiple tables if performance is > > being affected. > > > Another question - does having tables without explicit models break > > any CakePHP rules or conventions? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
