I had a similiar problem of needing to save coupons to orders. It is a HABTM relationship, but the order is saved well before the user tries to enter coupons. I ended up writing custom SQL to update the join table of the HABTM relationship. So, in this manner it is much like a belongsTo or hasMany relationship where you are accustomed to populating the join field yourself.
For most HABTM relationships CakePHP will be wonderful for retrieving the data. But since they are so complex and how people add and remove the joined data can vary you will be left to your own devices to manage the join table. I also saw a solution for in the join table of a HABTM relationship needed to have fields. Then, instead of HABTM of two models you would have three models and belongsTo and hasMany relationships between them. In this manner you would still be maintaining the join fields yourself, but in the more accustomed to manner of belongsTo and hasMany relationships that people seem so much more comfortable with. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
