Personally, I would keep the tables separate. I have never tried the tree behavior, but it sounds like it could harder to maintain as the table grows than separate tables. Will there ever be a need for the user to update fields from all tables in one form (your explaination didn't seem clear to me)? Are you using the HABTM relationships to pull all the desired info on a non-admin side of the application?
On May 12, 11:29 pm, "Dave Maharaj :: WidePixels.com" <[email protected]> wrote: > I have multiple HABTM tables for a user to select different options relating > to skills / preferences / experience. Would it be possible to use the tree > behaviour to group the options into 1 table and the user select from them > and only update the specific section? I am using multiple HABTM tables > simply because I need the user to update skills / preferences / experience > individually. Putting them all into one form updates them all and they are > all in different forms so that does not work. Is there a way to put all the > options into one table and if the user is updating their skills it will not > update their preferences or skills? > > What is the best approach to this? > > Dave --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
