My current problem: I have a large nightlife listings system, with many db tables all with a lot of relationships. On my index page I want to show small sets of information from a few of the tables.
At the moment I'm using requestAction to retrieve the data arrays from various models. The problem is some of those arrays will be huge once the real data is inserted into the db. For example if I want to display 5 imminent events I'm retrieving all related data in an array, when all I need is the date, name and type (stored in only 2 tables, overall the listings table relates to around 5 large tables). The page will have a few other sections like this, so I don't think it would be a good idea to be making really heavy demands on the db on the site's index page. I'm aiming for the minimum load on the server. So, what's the best method for dealing with this? My thinking was a few 'mini' models that don't have all the relationships defined (or maybe even custom queries that only pull out relevant fields). Any ideas would be greatly appreciated. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
