-
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
EF Core 3.1.4 Fails to read results from generated SQL #21026
Labels
area-query
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
customer-reported
punted-for-5.0
type-bug
Milestone
Comments
related issue: #20813 |
Thanks for linking. I tried the suggested workaround (add |
Similar to #19763. |
smitpatel
added
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
Mar 24, 2021
Poaching as I am fixing #19763 |
smitpatel
added a commit
that referenced
this issue
Mar 24, 2021
- Don't apply Include on entities with Include already applied - Update table references when pushing down select into left for set operation - Update identifiers after applying set operation if the projection removed exiting identifiers - Update SQL references in pending collection during push down Fix for the repro in #17337 Resolves #18738 Resolves #19763 Resolves #19947 Resolves #20813 Resolves #21026 Resolves #22222 Resolves #23676 Resolves #23720
smitpatel
added a commit
that referenced
this issue
Mar 24, 2021
- Don't apply Include on entities with Include already applied - Update table references when pushing down select into left for set operation - Update identifiers after applying set operation if the projection removed exiting identifiers - Update SQL references in pending collection during push down Fix for the repro in #17337 Resolves #18738 Resolves #19763 Resolves #19947 Resolves #20813 Resolves #21026 Resolves #22222 Resolves #23676 Resolves #23720 Resolves #24216
smitpatel
added a commit
that referenced
this issue
Mar 24, 2021
- Don't apply Include on entities with Include already applied - Update table references when pushing down select into left for set operation - Update identifiers after applying set operation if the projection removed exiting identifiers - Update SQL references in pending collection during push down Fix for the repro in #17337 Resolves #18738 Resolves #19763 Resolves #19947 Resolves #20813 Resolves #21026 Resolves #22222 Resolves #23676 Resolves #23720 Resolves #24216
smitpatel
added a commit
that referenced
this issue
Mar 25, 2021
- Don't apply Include on entities with Include already applied - Update table references when pushing down select into left for set operation - Update identifiers after applying set operation if the projection removed exiting identifiers - Update SQL references in pending collection during push down Fix for the repro in #17337 Resolves #18738 Resolves #19763 Resolves #19947 Resolves #20813 Resolves #21026 Resolves #22222 Resolves #23676 Resolves #23720 Resolves #24216
smitpatel
added a commit
that referenced
this issue
Mar 25, 2021
- Don't apply Include on entities with Include already applied - Update table references when pushing down select into left for set operation - Update identifiers after applying set operation if the projection removed exiting identifiers - Update SQL references in pending collection during push down Fix for the repro in #17337 Resolves #18738 Resolves #19763 Resolves #19947 Resolves #20813 Resolves #21026 Resolves #22222 Resolves #23676 Resolves #23720 Resolves #24216
bart-degreed
pushed a commit
to json-api-dotnet/JsonApiDotNetCore
that referenced
this issue
Apr 21, 2021
Verified fixed in EF Core 6 Preview 3, using Sqlite and PostgreSQL. Thanks a lot for fixing this! |
bart-degreed
pushed a commit
to json-api-dotnet/JsonApiDotNetCore
that referenced
this issue
Dec 2, 2021
bart-degreed
pushed a commit
to json-api-dotnet/JsonApiDotNetCore
that referenced
this issue
Dec 3, 2021
bart-degreed
pushed a commit
to json-api-dotnet/JsonApiDotNetCore
that referenced
this issue
Dec 3, 2021
bart-degreed
pushed a commit
to json-api-dotnet/JsonApiDotNetCore
that referenced
this issue
Dec 3, 2021
bart-degreed
pushed a commit
to json-api-dotnet/JsonApiDotNetCore
that referenced
this issue
Dec 3, 2021
bart-degreed
pushed a commit
to json-api-dotnet/JsonApiDotNetCore
that referenced
this issue
Dec 3, 2021
bart-degreed
pushed a commit
to json-api-dotnet/JsonApiDotNetCore
that referenced
this issue
Dec 3, 2021
bart-degreed
pushed a commit
to json-api-dotnet/JsonApiDotNetCore
that referenced
this issue
Dec 3, 2021
bart-degreed
pushed a commit
to json-api-dotnet/JsonApiDotNetCore
that referenced
this issue
Dec 3, 2021
bart-degreed
pushed a commit
to json-api-dotnet/JsonApiDotNetCore
that referenced
this issue
Dec 8, 2021
* Update to .NET 6 with EF Core 6 * Adapt to changes in nullability annotations * Adapt for breaking changes in PostgreSQL provider for EF Core 6 * Cleanup tests for handling special characters * Removed workaround for dotnet/efcore#21026 * Removed workaround for dotnet/aspnetcore#33394 * Removed workaround for dotnet/aspnetcore#32097 * Removed workaround for dotnet/efcore#21234 * Updated to latest Resharper version and removed workarounds for earlier versions * Applied new Resharper suggestions * Package updates * Renamed MSBuild variables * Inlined MSBuild variables that are used only once * Removed .BeCloseTo, now that fakers truncate time to whole milliseconds. Removed runtime casts, because the JSON deserializer now creates the correct types (based on the resource graph). * Narrow service scope lifetime * Enable registered services to dispose asynchronously, where possible * Workaround for bug in cleanupcode * Fixed detection of implicit many-to-many join entity in EF Core 6 * Activate implicit usings * Switched to file-scoped namespaces * Reformat solution * Added [NoResource] to suppress startup warning * Use Minimal Hosting APIs * Removed duplicate code * Corrected terminology for generic type usage * Fixed warning: Type 'KnownResource' does not contain any attributes * Updated roadmap and version table * Fixed: Override IIdentifiable.Id with custom capabilities no longer worked * Review feedback
nicolestandifer3
added a commit
to nicolestandifer3/DotNet-Core-Json-Api
that referenced
this issue
Aug 6, 2023
* Update to .NET 6 with EF Core 6 * Adapt to changes in nullability annotations * Adapt for breaking changes in PostgreSQL provider for EF Core 6 * Cleanup tests for handling special characters * Removed workaround for dotnet/efcore#21026 * Removed workaround for dotnet/aspnetcore#33394 * Removed workaround for dotnet/aspnetcore#32097 * Removed workaround for dotnet/efcore#21234 * Updated to latest Resharper version and removed workarounds for earlier versions * Applied new Resharper suggestions * Package updates * Renamed MSBuild variables * Inlined MSBuild variables that are used only once * Removed .BeCloseTo, now that fakers truncate time to whole milliseconds. Removed runtime casts, because the JSON deserializer now creates the correct types (based on the resource graph). * Narrow service scope lifetime * Enable registered services to dispose asynchronously, where possible * Workaround for bug in cleanupcode * Fixed detection of implicit many-to-many join entity in EF Core 6 * Activate implicit usings * Switched to file-scoped namespaces * Reformat solution * Added [NoResource] to suppress startup warning * Use Minimal Hosting APIs * Removed duplicate code * Corrected terminology for generic type usage * Fixed warning: Type 'KnownResource' does not contain any attributes * Updated roadmap and version table * Fixed: Override IIdentifiable.Id with custom capabilities no longer worked * Review feedback
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-query
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
customer-reported
punted-for-5.0
type-bug
When using Skip/Take in a nested query, an exception is thrown along the lines of "column t.AuthorId does not exist". I believe this is related to EF Core itself, because both PostgreSQL and SQL Server generate a similar error.
Steps to reproduce
I'm regenerating the database from code on each run, without adding any data.
Query:
Models:
Uncomment both lines in code above to cause the crash. Result when using PostgreSQL:
Stack trace:
When using SQL Server:
Stack trace:
The text was updated successfully, but these errors were encountered: