From b4bb4e89526dd6514c9040d006097bb283072d8c Mon Sep 17 00:00:00 2001 From: Federico Daniel Colombo Date: Wed, 22 Jan 2025 13:59:47 -0600 Subject: [PATCH] Update README.md --- src/Audit.EntityFramework/README.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/src/Audit.EntityFramework/README.md b/src/Audit.EntityFramework/README.md index 513eb0e4..41ff3b62 100644 --- a/src/Audit.EntityFramework/README.md +++ b/src/Audit.EntityFramework/README.md @@ -573,10 +573,12 @@ foreach(var entry in efEvent.Entries) If you plan to store the audit logs via EntityFramework, you can use the provided `EntityFrameworkDataProvider`. Use this to store the logs on audit tables handled by EntityFramework. -> **Note** +> **Notes** > -> Only the high-level audit events are processed by this data provider. Any other audit event, including the low-level events generated by the command interceptor, -> are ignored by the entity framework data provider. +> - Only the high-level audit events are processed by this data provider. Any other audit event, including the low-level events generated by the command interceptor, +> are ignored by the entity framework data provider. +> +> - This library also includes a [DbContext Data Provider](#generic-dbcontext-data-provider), which allows storing any type of audit events using an EF Core DbContext. For example, you want to audit `Order` and `OrderItem` tables into `Audit_Order` and `Audit_OrderItem` tables respectively, and the structure of the `Audit_*` tables mimic the audited table plus some fields like the event date, an action and the username: