-
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
Json: add support for Sqlite provider #28816
Labels
area-json
area-sqlite
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-enhancement
Milestone
Comments
maumar
added
customer-reported
area-sqlite
area-json
type-enhancement
and removed
customer-reported
labels
Aug 21, 2022
Consider a better exception if we don't get to this in 8: #29632 |
maumar
added a commit
that referenced
this issue
Feb 15, 2023
Adding support for Sqlite. Limitation: When accessing element of a JSON array we can only use constant values. Unlike Sql Server which supports parameters, columns or even arbitrary expressions. Fixes #28816
maumar
added a commit
that referenced
this issue
Feb 17, 2023
Adding support for Sqlite. Limitation: When accessing element of a JSON array we can only use constant values. Unlike Sql Server which supports parameters, columns or even arbitrary expressions. Fixes #28816
maumar
added a commit
that referenced
this issue
Feb 17, 2023
Adding support for Sqlite. Limitation: When accessing element of a JSON array we can only use constant values. Unlike Sql Server which supports parameters, columns or even arbitrary expressions. Fixes #28816
maumar
added a commit
that referenced
this issue
Feb 17, 2023
Adding support for Sqlite. Limitation: When accessing element of a JSON array we can only use constant values. Unlike Sql Server which supports parameters, columns or even arbitrary expressions. Fixes #28816
maumar
added
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
Feb 17, 2023
maumar
added a commit
that referenced
this issue
Feb 23, 2023
Adding support for Sqlite. Also adding some more query and update tests for properties with value converters. Limitation: When accessing element of a JSON array we can only use constant values. Unlike Sql Server which supports parameters, columns or even arbitrary expressions. Fixes #28816
maumar
added a commit
that referenced
this issue
Feb 23, 2023
Adding support for Sqlite. Also adding some more query and update tests for properties with value converters. Limitation: When accessing element of a JSON array we can only use constant values. Unlike Sql Server which supports parameters, columns or even arbitrary expressions. Fixes #28816
maumar
added a commit
that referenced
this issue
Feb 24, 2023
Adding support for Sqlite. Also adding some more query and update tests for properties with value converters. Fixes #28816
maumar
added a commit
that referenced
this issue
Feb 24, 2023
Adding support for Sqlite. Also adding some more query and update tests for properties with value converters. Fixes #28816
maumar
added a commit
that referenced
this issue
Feb 24, 2023
A better exception in 7 would've been nice too. This is what npgsql does: https://github.com/npgsql/efcore.pg/blob/03f9eb362cdd116b66af0c2c08983368b080d569/src/EFCore.PG/Infrastructure/Internal/NpgsqlModelValidator.cs#L197 I was really pulling my hair out over this one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-json
area-sqlite
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-enhancement
Currently Json support is only for SqlServer, we should light it up for sqlite also. Infrastructure is in relational so this shouldn't be too much work
The text was updated successfully, but these errors were encountered: