Delete via model instead of QueryBuilder

[andersLAL]

I use Translatable along with a model logging package that uses events to log changes. Deleting translations did not log (deleted event didn't fire) because they were deleted directly from the QueryBuilder, not model instances.

[dimsav]

Thank you @andersLAL!

[dimsav]

Fix was just released. :-)

[andersLAL]

Thanks :)

[Gummibeer]

Ok, but this is a massive Performance killer. Instead of one query it runs now 1+n in a foreach. And just to have events, which will decrease Performance also, is not a simple decision. :/

[dimsav]

Thank you @Gummibeer. Should we make it optional via configuration?

[Gummibeer]

@dimsav I think there are some options:

1. Write it in readme to let the users who need it override it by themself
2. Add a second Trait that does the first point
3. Add a configuration option to decide what to do
4. Send a custom event after the query delete

But adding a 1+n queries instead of 1 query without alternative is a downgrade for me. So there should be a way to get around.