Add possibility to add revision when we change something with many-to-many relationship.

[tommy7600]

Add possibility to add revision when we change something with many-to-many relationship.

[duellsy]

Open to pull requests on this one, I'm assuming you're talking about additional data updated on the pivot table?

[tommy7600]

Yes, I am talking about saving information from pivot table. I found solution to my problem, but it is very specific situation, so maybe we can even call my solution as a hack ;)
I opened this issue, because I don't have any idea how to expand your module and add generic solution for this kind of situations.

[duellsy]

Keen to see what you did

[deletosh]

@tommy7600 I'm also interested in seeing how you did this.

[kz]

@tommy7600 Ditto. I'm using attach() and detach(). Perhaps we could extend attach() and detach() and listen for when they are called, and then fire our own event which we listen to.

[oozrafa]

Any progress on this very important missing feature?

[gn0rt0n]

I really need this feature as well. I am open to sponsoring some development time on it. Let me know if you have an idea on how to implement this and roughly what it would take to get the work done.

[aske-cph]

I am also interested in this. Links to custom solutions also appreciated if development has stalled...

[molerat619]

any news 4 years later?

[jtomek]

any news 3 years later?

[MuriloChianfa]

The biggest problem is that we don't natively have Many to Many events.

If we use the laravel-pivot package, we can monitor the pivot updates and store new revisions for both many to many classes, we only have to wait the acceptance of changes in fico7489/laravel-pivot#91

In my use case, i have a many to many relation in ports to port group:

And the attach and detach events can now generate revisions as u can see in the "History changes" section on my software:

This will generate two revisions, one revision for each model, as we can see above.

Its simple to implement with laravel-pivot package, but im having trying yet

However if the intermediate table has some more fields, we would not be able to store it in the current "revisions" table, we would have to add some more fields to accommodate this, because in the database i have used the old_value and new_value to store the model target hahahaha.

Do you think it's a good idea to try adding some more fields to the table or is it worth creating another table of revisions for the case of Many to Many?

[duellsy]

@MuriloChianfa nice, will this support storing any changes that are made to other fields that might be on the pivot table, or limited only to the creation / destruction of a pivot?

[MuriloChianfa]

@duellsy only create and delete because, to add the pivot fields, we would have to add more fields to the revisions table, I imagine