On Feb 14, 3:21 pm, Josh Bassett <[email protected]> wrote: > I'm not really a fan of the idea for having to specify :_create in the > attributes for each nested model. That would make this feature quite > cumbersome to use. Also, I feel that would confuse things as you can > currently create nested models (albeit without a specific PK) without any > special :_create attribute. > > How about, as you initially suggested, if it just requires you to call > .unrestrict_primary_key in the parent model class?
I didn't edit my message properly before sending it. You can ignore the second paragraph, and just respond to this one: Your analysis is correct. I'm not sure this is a good candidate for supporting such code by default, though. Maybe there should be an easy to override method where you can pass in the reflection and attributes and it determines which method to run (create/update/ remove/ delete)? That would require some refactoring, but would allow you to easily get the behavior you want by overriding a simple method. Does that sound reasonable to you? Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk?hl=en.
