Thanks for the information. I was weighing my options. On one hand I wasn't sure how having hundreds or thousands of records would affect performance. On the other hand if I split the data across tables I would need to repeat the same query for each table to retrieve user information across multiple years. Also the issue of creating dynamic models may get a little tricky.
>From the help you guys have provided it appears that the way to go is to keep all my data in one table. That way the queries are less complicated and I wouldn't be violating any CakePHP rules =P. So what I'll do is create a single database table named time_sheets to hold all the application data. The table will look something like this: +================================================================+ | id (username) | year | jan | feb |... (etc)...| december | +================================================================+ That should solve my problem. So even if there are 1000 users over 50 years that's still a modest 50000 records which should be a piece of cake (no pun intended =) for MySQL. I'll probably start asking for contributors once I get the project up and running if anyone is interested. Either way I welcome any suggestions people have for this application. thanks again. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
