You can set custom table and key names for pretty much everything. Check this out for details: http://tempdocs.cakephp.org/#TOC59994. If you're implementing on Oracle and run into trouble, hop on IRC and ask for phishy.
On Jan 29, 6:03 am, "dr. Hannibal Lecter" <[EMAIL PROTECTED]> wrote: > Hi all, > > I'm just curious, I have three projects at work, websites written in > PHP, two of which are online and is about to go. I'd like to switch > them to Cake (of course), and my biggest concern is the database.. > > Databases for all three projects are "clones" of an oracle db from a > real-time / mission-critical system and cannot be changed. They are > mostly read-only and updated via custom php script (cron job) on > regular basis. Table names are all uppercase, in two out of three, the > field names are also uppercase, there are no 'id' fields as each table > has a custom primary key. > > Finally, my question is: I know I can make a single model work with a > single table ($useTable, $primaryKey etc..) but is it possible for the > whole site to work properly, when we consider all the custom relations > and primary keys, queries..? Are there any cock-ups I might run into? > Will there be any performance issues (in each database, there is a > huge-ass "transaction" table which is known to grow fast, we have 7 > digit numbers rowcount..)? > > Any advice? > > Thanks in advance, > dr. H. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
