Hi John, I tried your second approach but got a very large number of notices. I could turn these off of course, but I'd rather not them be generated in the first place if I can avoid it.
In my case, I have a member model and a character model. The member model has a primary_chracter_id while every character has a member_id. The idea being that a member can have many characters, but has one special character. Failing setting up both belongsTo and hasMany in this case, I was resigned to creating a flag in the character table for 'primary.' But I'd really prefer to track this information from the member table. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
