InnerEye-Gateway
InnerEye-Gateway copied to clipboard
Bump Microsoft.EntityFrameworkCore.Sqlite from 3.1.9 to 7.0.10 in /Source/Microsoft.Gateway
Bumps Microsoft.EntityFrameworkCore.Sqlite from 3.1.9 to 7.0.10.
Release notes
Sourced from Microsoft.EntityFrameworkCore.Sqlite's releases.
.NET 7.0.10
.NET 7.0.9
EF Core 7.0.8
This is a patch release of EF Core 7.0 containing only updates to dependencies. There are no additional fixes in this release beyond those already shipped in EF Core 7.0.7.
EF Core 7.0.7 is available on NuGet now. This is a patch release of EF Core 7 containing only important bug fixes:
- IndexOutOfRangeException in CreateNavigationExpansionExpression
- Linq select cannot project an entity containing both Json columns and ICollections
- Json: updating property with conversion from string to other type fails on sql server
- Duplicate table alias in generated select query (An item with the same key has already been added)
- InvalidOperationException when calling ExecuteUpdate with owned entity & using current value
- Query/Json: projecting entity collection along with json collection generates invalid shaper
- AutoInclude causes ExecuteDelete to fail
- Multiple LeftJoins (GroupJoins) lead to GroupJoin Exception when the same where is used twice
- SaveChanges circular dependency in unique unfiltered index (when change doesn't affect any column from unique index).
EF Core 7.0.5 is available on NuGet now. This is a patch release of EF Core 7 containing only important bug fixes:
- Can't add migration renaming a column on TPC root
- Scaffolded collection navigation properties do not have setters
- EF7 generating incorrect SQL for the Concat/Union All
- Added nullable property to Json mapped model resulting in errors instead of mapping non existing json property to null
EF Core 7.0.4
This is a patch release of EF Core 7.0 containing only important bug fixes:
- Exception replacing multi-level relationship in EF7
- Deletion can cause error "The association between entity types A and B has been severed..."
- Non-empty second migration in TPC scheme using inheritance
- Entity Framework Core 7 keeps creating the same migration for Nullable DateTime field
- TPC mapping strategy not respecting default database schema during migration
- Count after Take throws "No column name was specified for column 1 of 't'."
And for Microsoft.Data.Sqlite:
EF Core 7.0.3
This is a patch release of EF Core 7.0 containing only important bug fixes:
- Add-Migration fails with "An item with the same key has already been added" when renaming entity
- ExecuteUpdate fails when target entity has an owned entity
- EF Core 7 Rev eng: Missing HasForeignKey when referencing a navigation property with a unique constraint with DataAnnotations on
- Change in behaviour of CSharpHelper.Identifier(string name)
... (truncated)
Commits
8907538
Merge in 'release/7.0' changes3577954
Update dependencies from https://github.com/dotnet/arcade build 20230711.2 (#...a4937ab
Merge in 'release/7.0' changesec96a9a
Merge pull request #31225 from vseanreesermsft/internal-merge-7.0-2023-07-11-...c178722
Update global.json56dc4c2
Update global.jsond14f37e
Merge commit 'e00be013488a9a56a0e29230be0fe10026dbb209' into internal-merge-7...52e1a71
Merge in 'release/7.0' changes2669b8e
Merge in 'release/7.0' changesbbc6340
Merge branch 'release/6.0' into release/7.0- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)