You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when a model is changed, the observer was directly triggered.
Expected Behaviour
I wish a optional configurable behaviour, that a audit record is written by a job. Problem in my case is, that I am working with a big amount of data. I want audit any change but it's ok, when it's done some seconds later. In this situation I want win some time by move the auditing process to background.
Steps to Reproduce
Take existing model, change something and save.
Possible Solutions
Implement current observer auditing code into own class and call it directly or with job
The text was updated successfully, but these errors were encountered:
I see the value of the idea. A bunch of operations could be pushed back doing this. Maybe let the observer trigger a new event that could queue for doing the actual work.
Actual Behaviour
Currently, when a model is changed, the observer was directly triggered.
Expected Behaviour
I wish a optional configurable behaviour, that a audit record is written by a job. Problem in my case is, that I am working with a big amount of data. I want audit any change but it's ok, when it's done some seconds later. In this situation I want win some time by move the auditing process to background.
Steps to Reproduce
Take existing model, change something and save.
Possible Solutions
Implement current observer auditing code into own class and call it directly or with job
The text was updated successfully, but these errors were encountered: