Released: Jan 25, 2022

V9.16.1434 での更新項目

機能

• Added support for Microsoft .NET 6.0.

Entity Developer

• Changed behavior: Turning off the "Save connection to" option in Model Settings of Entity Framework Core Model wipes out connection string literal from the generated code.

Entity Framework support

• The SQL translation of the following class members used in LINQ query is now supported in Entity Framework Core 3, 5 and 6:
  • static method IsNullOrWhiteSpace() of the String class.
  • static property Today and instance property DayOfWeek of the DateTime class.
  • static methods Sqrt(), Max(), Min(), Log(), Log10(), Sin(), Cos(), Tan(), Asin(), Acos(), Atan(), Atan2() of the Math class.
• The SQL translation of the following class members used in LINQ query is now supported in Entity Framework Core 5 and 6:
  • static methods Abs(), Round(), Truncate(), Floor(), Ceiling(), Pow(), Sqrt(), Max(), Min(), Log(), Log10(), Sin(), Cos(), Tan(), Asin(), Acos(), Atan(), Atan2() of the MathF class.
• The SQL translation of the following class members used in LINQ query is now supported in Entity Framework Core 6:
  • static method Log2() of the Math and MathF classes.
• Mapping of internet/intranet data type System.Uri to Oracle string data types is now supported in Entity Framework Core 3, 5 and 6.
• Mapping of network data types System.Net.IPAddress and System.Net.NetworkInformation.PhysicalAddress to Oracle string data types is now supported in Entity Framework Core 5 and 6.
• Mapping of Oracle object types like MDSYS.SDO_GEOMETRY or Oracle user-defined object datatypes in a database to the OracleObject class in Entity Framework Core 3, 5 and 6 is now supported.
• The config.SpatialOptions.PreferSpatialOperators configuration option has been added (default value is False) to provide the possibility of using spatial operators instead of functions from the SDO_GEOM package.

不具合の修正

Entity Framework support

• Fixed the bug with auto savepoints enabled in Entity Framework Core 6 transactions.
• Fixed the bug with generating the "Value cannot be null" error when dropping indexes via Code-First Migrations in Entity Framework Core.
• Fixed the bug with a materialization used within the Let operator of LINQ query in Entity Framework 6.
• Fixed the bug with using .Contains with a collection within .Select of LINQ query in Entity Framework Core 2.