Hi thanks for the advice > If you were not planning already, any link table that has more than 2 >foreign keys should be a model so that you can easily manage them So for which tables should i be creating a model apart from those that have two foreign keys. I have not fully understood this after reading the manual, although I would do a model for the user and for the modules. i am not sure about the others though, any help on that?
> DRY - module_name -> name, module_code -> code, role_name -> name, > task_name -> name, task_order -> order Im sorry but i did not understand what DRY means, should i change those names like module_name becomes name etc? approved - do you need this? e.g. if the approval date is not set, > it's not approved. alt. use a status The system should allow the administrator to approve the review when everyone has put in their contributions, thus he would mark the review as approved and put in the date of approval, I guess I could therefore do away with the status field and just leave the date rest i understood and agree with you, thanks again! On Jul 23, 8:16 am, AD7six <[EMAIL PROTECTED]> wrote: > On Jul 22, 9:23 pm, rtanz <[EMAIL PROTECTED]> wrote: > <snip> > > > I would like some feedback from more experienced users as to whether these > > tables are correct for cake implementation > > Hi rtanz, > > You can use a table with whatever names you like with cake, as such > it's almost impossible to choose table names that are 'incorrect' for > use with cake. > > If your table names or keys etc. don't follow conventions (http:// > manual.cakephp.org/appendix/conventions), you just need to tell cake > what to expect. > > However: > If you add the 2 datetime fields modified and created (to anything > except a join table), they get populated automatically with what you > would expect > If you were not planning already, any link table that has more than 2 > foreign keys should be a model so that you can easily manage them. You > can if you wish and it's appropriate change this in the future to be > a 'conditional' habtm but starting out using a model would be a lot > easier. > DRY - module_name -> name, module_code -> code, role_name -> name, > task_name -> name, task_order -> order > You don' t need the date_created field in your modules tasks users > table if you follow conventions > approved - do you need this? e.g. if the approval date is not set, > it's not approved. alt. use a status > year_delivered - why not store the delivery date? > task_complete - why not store a status? > > A status field rather than a boolean "completed" would give you the > advantage that you can then add another status if necessary such as > deferred, canceled, obsolete, pending, started, assigned etc. > > hth, > > AD --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
