- ABP Framework version: v4.0.0
- UI type: MVC
- Tiered (MVC) or Identity Server Seperated (Angular): yes / no
- Exception message and stack trace:
- Steps to reproduce the issue:
- **Database: MongoDB
Hi,
I am implementing my own entity change tracking and am using MongoDB.
There is a bug, which means that the sorting is only being applied to the current page of entity change results. https://github.com/abpframework/abp/blob/f4c7def47a97c77e4fa2813f52e8ebe61598f095/modules/audit-logging/src/Volo.Abp.AuditLogging.MongoDB/Volo/Abp/AuditLogging/MongoDB/MongoAuditLogRepository.cs#L179
Paging should be performed after the sort, same as this line: https://github.com/abpframework/abp/blob/f4c7def47a97c77e4fa2813f52e8ebe61598f095/modules/audit-logging/src/Volo.Abp.AuditLogging.MongoDB/Volo/Abp/AuditLogging/MongoDB/MongoAuditLogRepository.cs#L58
Best regards,
Mike
3 Answer(s)
-
0
hi michael,
yeah that seems to be a bug. sorting must be put before the fetch operation. Even though it's on the open-source side, nobody has reported this yet. Maybe because MongoDB is not used by many people. I created an issue on the ABP repo. Also I increased your question credits. Let's track the issue at https://github.com/abpframework/abp/issues/6706
-
0
Thanks for that. We actually purchased the upgrade to the business license recently, but the question credits did not increase with the upgrade. Maybe you could bump it up a bit more? Hopefully, I won't need them, but you never know.
-
0
now you have enough credits :)
