Langdon's right. Bake.php is the end all be all of cake model/view/ controller generation.
Also, take a look at this article: http://www.littlehart.net/atthekeyboard/2007/07/11/why-code-generation-just-works-damnit/ On Aug 7, 12:21 am, modfather <[EMAIL PROTECTED]> wrote: > Hello ladies and gents, > I'll start of by admitting this might not be specifically a "cake" > question but it does pose some questions about the usability of cake > (from my perspective). > > I am in the process of updating/re-designing a site. One part of this > site contains what is called "msds" sheets. The site includes > approximately 50 of these sheets.An example of this sheet is > athttp://apexlabs.com.au/veterinary/MSDS/18/Apex+Carprofen+Tablets > > The data contained in the msds sheets is from a mysql database. These > MSDS includes data from over 60 tables. > > As far as i can tell i will have to produce at least 60 model pages > ( to correspond with associated models) and my msds model will contain > an array will contain a massive "$belongsTo" array - which will also > be affected by mysql 4.1 join limitations, lack of views etc. > > class Msds extends AppModel { > > var $name = 'Msds'; > var $useTable = 'Msds'; > var $belongsTo = array( > 'Category' =>array( > 'className' => 'Category' > ), > 'RecommendedUse' => array( > 'className' => 'RecommendedUse', > 'foreignKey' => 'recommended_use_id' > ), > 'Classification' =>array( > 'className' => 'Classification', > 'foreignKey' => 'classification_id' > ) > > I feel this is a fairly tedious process , so the question is - is > there another way to build this or am i being lazy? --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
