While is best practice to start with you data architecture, Cake does have certain requirements to keep in mind for when you do get around to code generating. These are worth mentioning, even if they seem academic.
* Obviously, you want to follow Cake's naming conventions for tables and fields. http://book.cakephp.org/2.0/en/getting-started/cakephp-conventions.html#model-and-database-conventions * Cake requires requires a single-field primary key (by convention, named "id"). This should be either an auto-incrementing integer or UUID. * Cake cannot work with composite primary keys, so you always have the "id" field described above. * The linking table for many-to-many relations should be named properly ("tableA_tableB," with the tables in alphabetic order) and does NOT require an id field, although you can (and maybe should) add one. This allows you to skip the trouble of creating model files for these linking tables in your app. If you plan on saving any other data in the linking table, then you will need to have an id field and create a model file for the table. I can't think of any others, but if you follow these it will ease your path with Cake when it comes time actually crunch the code. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
