On Feb 25, 10:10 pm, Marcelo Andrade <[email protected]> wrote: > "The framework is inadequate to create new records in > tables that have only one autoincrement (or serial) field"
If I'm understanding this correctly, this is perfectly fine as far as CakePHP is concerned. In fact, most new database tables (and many CakePHP tutorials out there) created to take advantage of CakePHP's DB automagicness almost always use an autoincrementing field for the primary key. So that is not an issue at all. > "The framework requires a database that follows a predefined > convention. So it's impracticable to use it with existing > databases from legacy systems. This isn't true. CakePHP can use pre-existing tables just fine. For example, one can simply specify the table name to use in the model class: var $useTable = 'PreExistingTableName'; You can also define many other model attributes to allow CakePHP to work with pre-existing databases. Many of these attributes are listed in the CakePHP manual: http://book.cakephp.org/view/71/Model-Attributes Also, model associations are flexible in that you can do things like specify custom queries when finding, deleting, and inserting records if you need to. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~----------~----~----~----~------~----~------~--~---
