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
Long story short is I would expect if ReplaceReadEntities = true for the BulkConfig options for a .BulkRead(Async) that I would end up with an empty list if there were no matches on the database. Instead, we end up with the original list that is not updated similar to if we did not have ReplaceReadEntities.
Right now we are having to rely on a specific field we are 99% sure should never be a default value to validate if the entities were actually replaced, however this is not optimal and would not work for all use cases.
This is with a SQL Server database if that matters.
The text was updated successfully, but these errors were encountered:
Yes that seems to be in line with what I see happening when there are matches and ReplaceReadEntities = true. An empty list would signify there were no matches just like a N sized list indicates there were N matches
Long story short is I would expect if ReplaceReadEntities = true for the BulkConfig options for a .BulkRead(Async) that I would end up with an empty list if there were no matches on the database. Instead, we end up with the original list that is not updated similar to if we did not have ReplaceReadEntities.
Right now we are having to rely on a specific field we are 99% sure should never be a default value to validate if the entities were actually replaced, however this is not optimal and would not work for all use cases.
This is with a SQL Server database if that matters.
The text was updated successfully, but these errors were encountered: