-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duplicated audit entries #330
Comments
We need more info to reproduce an error. |
@samuel4x4 I confirm the need to get more information about your current config/setup, I haven't been able to reproduce the issue on my side. |
@samuel4x4 any chance to get more information about your current config/setup? |
Samy issue.
dh_auditor.yaml: dh_auditor:
timezone: 'Europe/Paris'
enabled: true
providers:
doctrine:
table_prefix: null
table_suffix: '_audit'
ignored_columns:
- createdAt
- updatedAt
- id
entities:
App\Data\Entity\LMS\Course: ~ services.yaml: DH\Auditor\Provider\Doctrine\Auditing\Transaction\TransactionManager:
arguments: [ '@DH\Auditor\Provider\Doctrine\DoctrineProvider' ]
DH\Auditor\Provider\Doctrine\Auditing\Event\DoctrineSubscriber:
arguments: [ '@DH\Auditor\Provider\Doctrine\Auditing\Transaction\TransactionManager' ]
tags:
- { name: doctrine.event_subscriber } |
@Navds Why you define Auditor services manually? It defines automatically within container compile time. |
I don't remember exactly why but it didn't work before and I followed the advice at #251 |
auditor-bundle
versionSummary
Entries are duplicated on the audit database tables for all actions: INSERT, UPDATE, ASSOCIATE.
Current behavior
Multiple similar entries are added on the entity audit tables for the same object_id, including for INSERT operation, which can't really happen with the same id. I have for example up to 12 similar entries sometimes.
How to reproduce
Any normal operation executed on an audited entity generates duplicated audit entries.
Expected behavior
Audit entries should be added only once on the database.
Example:
The text was updated successfully, but these errors were encountered: