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
| Bug? | no
| New Feature? |yes
| Framework | Laravel
| Framework version | 8.12
| Package version | 12.0
| PHP version | ^8.0
Actual Behaviour
Tags are stored in tags column of Audit Model
Expected Behaviour
I would like to be able to store tags in a seperate table, because when multiple tags are inside "tags" column filtering using SQL becomes very slow since one cannot use indexing.
Possible Solutions
Instead of directly calling create on the implementation at
one could use a UserCreate service that is called (just as we have the resolver services). In this service class, only the create method is called.
Thus the UserCreate service could be overwritten in the configs (just as the resolvers). People could then choose freely if they would like to store the tags in a different table inside their custom UserCreate service.
If you agree with this small change, I would like to create the MR.
The text was updated successfully, but these errors were encountered:
Is there any update on this matter? We have a sizable project, and the audit table contains millions of records. Therefore, searching using LIKE is an extremely time-consuming task.
Is there any update on this matter? We have a sizable project, and the audit table contains millions of records. Therefore, searching using LIKE is an extremely time-consuming task.
Yes. It will happen. But I can't put a date on it yet
| Bug? | no
| New Feature? |yes
| Framework | Laravel
| Framework version | 8.12
| Package version | 12.0
| PHP version | ^8.0
Actual Behaviour
Tags are stored in tags column of Audit Model
Expected Behaviour
I would like to be able to store tags in a seperate table, because when multiple tags are inside "tags" column filtering using SQL becomes very slow since one cannot use indexing.
Possible Solutions
Instead of directly calling create on the implementation at
laravel-auditing/src/Drivers/Database.php
Line 19 in 5659c73
Thus the UserCreate service could be overwritten in the configs (just as the resolvers). People could then choose freely if they would like to store the
tags
in a different table inside their custom UserCreate service.If you agree with this small change, I would like to create the MR.
The text was updated successfully, but these errors were encountered: