Kevin,
i'm still not sure that's a good idea. When an admin goes to update an Attribute, validation would allow them to leave required fields empty. The database would object, since those fields are set NOT NULL. i'm not sure how that objection is handled if i didn't prevent it with the validation...
If i'm forced to assume a save that uses the belongsToMany structure & associated entity option will ALWAYS send a save to the associated table and the joint table between them, then i'd rather not use that approach. Is there a way i can structure my form & generate the entity so i only send data to Listings & ListingsAttributes? Or am i forced to use the saved ID from Listings & do a separate replace/save to ListingsAttributes?
Thanks for the continued help.
-joe
--
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP
---
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscribe@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment