well it is possible to use more then 1 database (you'll see that the default configuration config/database.php has 2 presets, but you can enter as many as you want) but i'm pretty sure that this is not convinced.
most, if not all, websites/applications use 1 database, which holds many tables , and the most common use is that each table is used by 1 model (and some tables are for many:many relations but that's not very important now). most controllers use 1 model, but it's very common to create controllers that don't use models, or use several, whatever you want. the process is pretty easy. you could also use requestaction offcourse to "get" chunks that you need in your view or other data. this is all piece of cake.. (get it?) i think that this should already clear up some confusion the rest of your questions comes down to this: just make a logical design for your entities (models) and how they relate. (eg club hasone venue, venue belongsto club, music type habtm club, club hasmany review, review belongsto club, etc etc. associations are really well explained in the manual, chapter models) it certainly needs some thinking (and it's better to think first, and code afterwards), but if it's done well, everything else is a snap. and i would even say that the webapplication that you are building could serve as a great example for cake, because it is all possible without problems. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
