Thanks nate.
On Jan 24, 1:51 pm, nate <[EMAIL PROTECTED]> wrote:
> class Post extends AppModel {
>
> var $hasAndBelongsToMany = array("Tag" => array("with" =>
> "Whatever", "unique" => false));
>
> }
>
> On Jan 24, 2:48 pm, "[EMAIL PROTECTED]"
>
> <[EMAIL PROTECTED]> wrote:
> > I'm back to thinking I'm right...someone please prove me wrong here.
>
> > If $fieldList is specified for Model::save() shouldn't it at least
> > THEN ignore the 'with' relationships? It currently does the DELETE
> > query even in this case.
>
> > The only other option is saveField() but that is really wasteful for
> > the multiple queries.
>
> > On Jan 24, 1:31 pm, "[EMAIL PROTECTED]"
>
> > <[EMAIL PROTECTED]> wrote:
> > > yeah that seems like a logical thing to do
>
> > > On Jan 24, 1:30 pm, "[EMAIL PROTECTED]"
>
> > > <[EMAIL PROTECTED]> wrote:
> > > > Hey Eric, why don't you just use saveField() in this situation?
>
> > > > On Jan 24, 1:20 pm, "[EMAIL PROTECTED]"
>
> > > > <[EMAIL PROTECTED]> wrote:
> > > > > I don't know why HABTM relationships are deleted automatically on a
> > > > > Model::save() in the first place, but is this really necessary for the
> > > > > 'with' relationships too? They are practically standalone models so
> > > > > shouldn't there be an option to preserve the current 'with'
> > > > > relationships?
>
> > > > > I can unbind() them, but I'm questioning that this is a logical thing
> > > > > to do before every single save() where I'm just updating the original
> > > > > model.
>
> > > > > Core contributors have any input on this?
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
