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
We are encountering an issue while using BulkMerge with IncludeGraphOperationBuilder in PostgreSQL. The configuration bulk.IsReadOnly = true is supposed to prevent updates for an entity, and this functionality works as expected in MSSQL. However, in PostgreSQL, it does not behave correctly and upserts are still being attempted.
Further technical details
EF Core version: 9.0.0
EF Extensions version: 9.103.6.3
Kindly investigate this issue and provide a fix or suggestion. Let me know if further details or testing are needed.
As we are migrating from MSSQL to PostgreSQL, it would be helpful if you could provide a comprehensive list of features and options that are supported in MSSQL but not in PostgreSQL. I couldn't find anything in the documentation.
Currently, I am manually checking for compatibility in each module, which is both time-consuming and challenging. A documented list would help us plan effectively.
I'm dedicating the whole of December month to improving the documentation (one of the reasons we refuse at this moment a lot of new features/requests as otherwise I'm only able to do the code review of my developers).
We will surely try our best to add more details about all our options.
Description
Hi Team,
We are encountering an issue while using BulkMerge with IncludeGraphOperationBuilder in PostgreSQL. The configuration
bulk.IsReadOnly = true
is supposed to prevent updates for an entity, and this functionality works as expected in MSSQL. However, in PostgreSQL, it does not behave correctly and upserts are still being attempted.Further technical details
Kindly investigate this issue and provide a fix or suggestion. Let me know if further details or testing are needed.
@JonathanMagnan
Thanks
--Balaji
The text was updated successfully, but these errors were encountered: