-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Can't map Dictionary<string,object> (e.g. to JSON) since it's detected as a property bag #26903
Comments
Note from triage: @roji to give this a try on current main. |
Confirmed that the exception still occurs on latest main (590c783):
|
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Related to #28871 |
|
Any chance this is coming in EF core 9? |
This issue is in the Backlog milestone. This means that it is not planned for the next release. We will re-assess the backlog following this release and consider this item at that time. However, keep in mind that there are many other high priority features with which it will be competing for resources, see Release planning process. Make sure to vote (👍) for this issue if it is important to you. |
With (PostgreSQL) native JSON support, it's useful to map Dictionary directly to JSON columns. This works e.g. for
Dictionary<string,string>
, but fails forDictionary<string,object>
since the property is detected as a property bag:The exception:
We may want to stop detecting property bags if column has an explicit store type. Following on how type converters work, this can be worked around by configuring the property with
.Metadata.SetProviderClrType(null)
./cc @AndriySvyryd
Originally filed by @ColinZeb in npgsql/efcore.pg#2134
The text was updated successfully, but these errors were encountered: