It sounds like a HABTM table is precisely what you need. Please elaborate on your requirement 'cannot do HABTM due to storing meta info'. - Rob
On Friday, May 25, 2012 9:09:59 PM UTC-4, Benjamin Allison wrote: > > I have two models: Users and Surveys. In my Users "index" view, each User > row has two select lists that are populated with the names of all the > available Surveys. > > The idea is to allow someone to assign two Surveys to each user, right > from the Index page. The associations take place via a hasMany Through > association: the intermediary model is called SurveyAssignments (I can't do > HABTM because I'm storing meta info). > > What I'm struggling with is that I can't figure out how to save all those > associations, from one page, or how to account for each user's specifica > association state: some users will have association records, some will not. > Some will need associations created, others changed or removed. > > I would like to avoid large complicated nests of if statements! > > How can I account for multiple records one on page, and handle all of > their unique association states without getting overly bloated or > complex? Any ideas? > -- 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
