* Improve the migrations.
- Missing index sort order in model and sql
- When altering a column to non-nullable, have an UPDATE to make any NULL values the default value
* Changes to comments produce no SQL output as we don't handle comments
* update ef core
* catch exceptions on some newly failing tests. Bug in upstream
* [GitHub Actions] Update green tests.
---------
Co-authored-by: github-actions <github-actions@github.com>
* fix array index and array length for byte arrays
* [GitHub Actions] Update green tests.
* Fix Contains with byte array. and fix getting length if an odd number of bytes
* fix array index and array length for byte arrays
* Fix Contains with byte array. and fix getting length if an odd number of bytes
* Enforce an optin methodology using EF.Functions for the byte array length due to certain situations with unicode strings
* Split error message and details into 2 parts
* Fix parameter config for decimal and long when using odbc
* DateTime.Date needs its output type mapping to be a datetime
* use decimal as base for currency
* update tests
* Fix DateTime.Date null checking
* Move the SkipTake to its own processor
This handles the queries with Offset and Limit better as there are other linq methods that manage to set the Limit (e.g. First)
When the option to use the short text (aka varchar) as the default for System.String, if we have a attribute or fluent api that sets its max length to greater than 255 it would stay as varchar, which is invalid with a length greater than 255.
Fix this to upgrade this instance to an unbounded string. This will use the long text/memo data type in Jet (longchar)
MS Access does not have a DateTimeOffset data type so the value should be converted to UTC and saved as a normal date/time
This fixes 2 things
Regression in 7.0 series where the DateTimeOffset was being written as Local time and not UTC.
When reading the value and converting from a DateTime, the Offset value ended up being implicitly set to the systems local time zone offset. A DateTimeOffset from a UTC value should actually have an offset of 0. This has been wrong since the 2.2 series
* Add expression visitor to locate a scalar subquery. Handles finding deeper subqueries better than original code.
Also handle the case where the expression can be regarded as scalar (i.e. has a TOP 1 and projects only one field). In that case we rewrite the projections so that we take out any previously added projections as it is clear we are not needing it higher up in the SQL
Christopher Jolly
github-actions