-
Notifications
You must be signed in to change notification settings - Fork 86
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
PostgreSql: Audit does not work for BulkUpdate #102
Comments
Hello @ElenaShlykova , Thank you for reporting, My developer will look at it. Best Regards, Jon |
Hi @JonathanMagnan - have you been able to look into this yet? |
Hi @JonathanMagnan - bump :) |
Hello @karolswdev , Sorry for the long delay, Unfortunately, there is no good news for this one. Making it work correctly with Best Regards, Jon |
Hi @JonathanMagnan, What is alternative for this ? Can you provide and example ? |
Hello @karolswdev , @dpatusb , It took us some time but the v5.0.0 has been finally released. The If you have the chance to test it, let us know if everything works as expected. Best Regards, Jon |
@ElenaShlykova - looks like they've made a major change. Could be a positive impact for us. |
Hello,
We noticed that the audit does not work correctly with the postgreSQL database.
When updating a record with BulkUpdate, the old value is equal to the new value.
In my example, I am creating a test entity with Value = 'TestValue'. After that, I update the Value property to 'NewValue' and update the record with BulkUpdate. After that, I see that the record in the database has been updated.
The problem is in dapperAuditEntries the old value is equal to the new value:
I expect the old value to be 'TestValue'.
Mapping:
This works well for mssql.
The text was updated successfully, but these errors were encountered: