sicapitan wrote: > just seemed a bit excessive to have 1,000,000 files for 1,000,000 tables
Have you ever been to an airport in the US, and seen that big glass container that shows all the things you're not allowed to bring on an airplane? Well, at the John Wayne Airport in Orange County, California, one of the things in the container is a leaf blower (http://www.hardwareworld.com/files/pi/bM/F/TVE3.jpg). The point of all this is that if you have an application that actually needs a million tables, it's sort of like having a job that requires you to bring a leaf blower on an airplane: you really need to stop and rethink a few things. That said, I'm currently in the process of writing an add-on to an application that has 663 tables. Yes, some of them are a bit redundant, and fortunately I don't have to use all of them, but I did try once, and a few things struck me: (1) Since PHP is such a kick-ass language, and since Cake is such a kick-ass framework, it took me about 5 minutes to put together a script that generated model files for all 663 tables (some of them were join tables, so I had to go back and delete those). (2) Since the client's production server has APC installed, loading 600+ models had surprisingly little impact on performance (probably because most of them were empty shell classes). In conclusion, stop complaining. Having to have one whole file for every table you want to use in an application is a pathetically small price to pay when you consider that the majority of the time, this is just about the best way out there to structure any application, let alone a PHP application. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
