The Bakery Everything CakePHP

I am trying to use this code and when i do this:

$this->Model->habtmDelete('Blah', 1, 1);

it runs this sql query:

Query: habtmDelete

I am running this from the controller, so is that the problem or is it something with the new cake 1.2.x.x ?
Please Help.

I found it necessary to augment the unbindAll function to allow nested unbindings.


/**
     * Allows you to quickly unbind all of a model's associations and exempts
     * those specified in the second parameter.
     *
     * Usage:
     *    $this->Model->unbindAll(); // unbinds associations
     *    $this->Model->unbindAll(array(
     *        'Child1',
     *        'Child2' => array('GrandChild1' => array('GreatGrandChild1')),
     *    ));
     */
    function unbindAll(&$model, $exceptions = array()) {
        
        // Make sure array keys are all on they key side
        foreach($exceptions as $key => $value) {
            if (is_numeric($key)) {
                unset($exceptions[$key]);
                $exceptions[$value] = null;
            }
        }
        
        // Determine which models need unbinding
        $unbind = array();
        $exceptionKeys = array_keys($exceptions);
        foreach($model->__associations as $type) {
            foreach($model->{$type} as $assoc=>$assocData) {
                if(!in_array($assoc, $exceptionKeys)) {
                    $unbind[$type][] = $assoc;
                }
            }
        }
        
        // Recursively unbind child models
        foreach ($exceptions as $key => $value) {
               $this->unbindAll($model->$key, (!empty($value) ? $value : array()));
        }
        
        // Unbind any models not exempted
        if (count($unbind) > 0) {
            $model->unbindModel($unbind);
        }
    }


I have a strange issue:

I have two models that have a HABTM connection. The models are User and Publication. When I get an object (of the model Publication) and change a value like this:

$data['Publication']['key'] = $value;
$this->Publication->save($data['Publication']);

What happens now is that the row is updated but in the join table the "user_id" gets set to NULL.

What is going on here?

I can fix it by doing this after the store, but this seems a lame way of doing it:

$this->Publication->habtmAdd('User', $data['Publication']['id'], $user['id']);

I found that I often needed a method to check whether two models had been associated. I've added this code to mine:

/**
* Checks to see if two models are bound together
*/
function habtmCheck(&$model, $assoc, $id, $assocIds) {
$data = $this->__habtmFind($model, $assoc, $id);
return !empty($data[$assoc][$assoc]);
}

I apologize for the lack of update on my comment.
Franlkly at the moment i did not need it. It shoudn't be hard to implement. Hopefully in the next few days I will post an updated version. BTW thanks, Brandon Parise for the behaviour..=)

@12:

the following function can be used in conjunction with that specified in comment 12 above, in order to update the extra fields associated with the habtm join table.

for example:

post_id tag_id relevance
1 2 50

$this->Post->habtmUpdate('Tag', 1, 2, array('relevance' => 60));

yields

post_id tag_id relevance
1 2 60

function habtmUpdate(&$model, $assoc, $id, $assoc_ids, $extra = array() ) {
if(!is_array($assoc_ids)) {
$assoc_ids = array($assoc_ids);
}

// make sure the association exists
if(isset($model->hasAndBelongsToMany[$assoc])) {
$data = $this->__habtmFind($model, $assoc, $id);
debug($data);

// no data to update
if(empty($data)) {
return false;
}

// save extra fields
$joinTable = $model->hasAndBelongsToMany[$assoc]['joinTable'];
$associationForeignKey = $model->hasAndBelongsToMany[$assoc]['associationForeignKey'];
$foreignKey = $model->hasAndBelongsToMany[$assoc]['foreignKey'];
$thisid = $data['Sale']['id'];

if( !empty( $joinTable ) && count( $extra) ){
$sql = array();
foreach( $extra as $key => $value )
$sql[] = $key . " = '". addslashes($value) . "'";

$success = $model->query( "UPDATE $joinTable set ".implode( "," , $sql )." WHERE $foreignKey = $thisid AND $associationForeignKey IN ( ". implode( " , " , $assoc_ids ) ." )");
}
return $success;
}
// association doesn't exist, return false
return false;
}




the code above zeroes out all extra data entries for every association for a model when deleting one of a model's associations by using habtmDelete above. I am working on a functioning version.

@1 - would love to see your implementation for HABTM relationships that require extra data.

@12 - this doesn't seem to fully work, as the extra fields end up being emptied during the add process. Currently, all foreign keys are temporarily stored, then all HABTM relationships are deleted, then all HABTM relationships are re-added but without the extra data they had before. Only the new HABTM relationship being added has its extra data stored.

I'd love to see if someone has some insight on getting this to work with extra data. Thanks :)

I had an issue with adding a HABTM relationship to a self-referencing model, where I needed to turn off auto-validation when saving the data.

I don't think this solves the root of the problem, but turning off validation in habtmAdd() worked:


return $model->save($data, false);


It seems you haven't had the time to add extra fields to the association so i modified your add function with this functionality. Its working for me but use with care

To use:

$this->Post->habtmAdd('Tag', 1, 1 , array( 'tag_type' => 2) );

function habtmAdd(&$model, $assoc, $id, $assoc_ids , $extra = array() ) {
if(!is_array($assoc_ids)) {
$assoc_ids = array($assoc_ids);
}

// make sure the association exists
if(isset($model->hasAndBelongsToMany[$assoc])) {

$data = $this->__habtmFind($model, $assoc, $id);

// no data to update
if(empty($data)) {
return false;
}

// important to use array_unique() since merging will add
// non-unique values to the array.
$data[$assoc][$assoc] = array_unique(am($data[$assoc][$assoc], $assoc_ids));

$success = $model->save($data);

// save extra fields
$joinTable = $model->hasAndBelongsToMany[$assoc]['joinTable'];
$associationForeignKey = $model->hasAndBelongsToMany[$assoc]['associationForeignKey'];
if( $success && !empty( $joinTable ) && count( $extra) ){
$sql = array();
foreach( $extra as $key => $value )
$sql[] = $key . " = '". addslashes($value) . "'";

$model->query( "UPDATE $joinTable set ".implode( "," , $sql )." WHERE $associationForeignKey IN ( ". implode( " , " , $assoc_ids ) ." )");
}

return $success;
}

// association doesn't exist, return false
return false;
}

Can anyone provide some direction for modifying this for version 1.1? I've not had much success thus far.

Thanks.

This is wonderful, I have been lost for a week trying to get associations to save, then Grant pointed me to this and within 2 minutes it was done. Thank you.

Awesome article.. this gets added to my "essential cake reading material" list.

Just wondering how the extra field functionality is coming along.

I'm also looking forward to the functionality you describe; it will be very useful!

...looking forward to seeing it :-)

I will add the functionality this weekend

I would indeed be happy if you added the ability to add extra field data to the HABTM cross table.

I could use the functionality that you mentioned above.

If there is any demand to allow you to save more than just the foreignKey / associationForiegnKey to the HABTM cross table I will add it. Example:

Post HABTM Tag and `posts_tags` has a field `other_field`

$this->Post->habtmAdd('Tag', 1, array(
array('tag_id' => 1, 'other_field' => '123ABC'),
array('tag_id' => 2, 'other_field' => '123ABC'),
);