…#34263)

Closes #34295

Allow to specify a target migration in Migrate call
Warn on Migrate when there are pending model changes

Fixes #17568
Fixes #33732
Fixes #34196

Use a single transaction for all migrations in the script

Fixes #17578
Fixes #22616

Since #34080 the SqlServer provider uses XOR to avoid converting to/from predicates when negating BIT expressions.
It is actually possible to simply use ~ on BIT values and this changeset implements this.

Fixes #34213

* Add minimal support for `ExpressionType.OnesComplement` It is currently only supported in the final part of SqlServer translation pipeline.
* Use `~` for negating boolean values Instead of `x ^ 1`, use the `~x` expression when translating boolean values in SqlServer.

…0728.5 (#34311)

[main] Update dependencies from dotnet/runtime

* Propagate `allowOptimizedExpansion` to `CASE` results

If the `CASE` is used in a context that allows optimizations (predicates, where
NULL and FALSE are equivalent), the same holds for each of its results.

Bumps [Microsoft.Azure.Cosmos](https://github.com/Azure/azure-cosmos-dotnet-v3) from 3.41.0 to 3.42.0.
- [Release notes](https://github.com/Azure/azure-cosmos-dotnet-v3/releases)
- [Changelog](https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/changelog.md)
- [Commits](Azure/azure-cosmos-dotnet-v3@3.41.0...3.42.0)

---
updated-dependencies:
- dependency-name: Microsoft.Azure.Cosmos
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Closes #34256

Change ReplacingExpressionVisitor.Replace to IReadOnlyList<Expression> parameters
Make ReaderColumn.GetFieldValueExpression and the new constructor experimental.
Make ReaderColumn.Create experimental.
Make ReaderColumn<T> constructor experimental.

…te code with labels that are not uniquified (#34323)

Problem was that when we generate shaper for extracting json values from the reader (streaming) we use hard-coded name for a label that's used in the loop going through json properties. This is fine for normal scenarios, since compiler can figure out the right label to jump to based on scope/reference, but when we generate c# code from that expression, we run into issues for case of nested JSON.
Existing code already works if the label is not named explicitly - LinqToCSharpSyntaxTranslator generates names for unnamed labels and uniquifies the names when needed. Fix is to add the uniquification to all labels, not only the unnamed one.

Also fixed another small bug in LinqToCSharpSyntaxTranslator encountered in the testing - when we process LambdaExpression and are dealing with lifted statements (that need to be incorporated into the lambda body), we assumed it would always be a single expression, but it could also be a block. Fix is to add handling for the block case, which is simply pre-pending lifted statements to the ones already in the block.

Added JSON entites to Blog so that we can test the scenario, also added some posts (there were none) for cases which don't work with JSON entities, e.g. set ops.

Fixes #34056

Fixes #34218

… support (#34325)

Fixes #34324

…o_subquery (#34326)

Fixes #34316

…725.3 (#34310)

[main] Update dependencies from dotnet/arcade

…t entity in the hierarchy by default (#34252)

Fixes #34176

Also, model validation.

* Add back support for Cosmos nested dictionaries

Fixes #34105

This code will be consolidated with the relational UTF8 JSON code when #29825 is implemented. For now, just adding back what was already in Cosmos.

* Review updates