New build of dotConnect for Oracle 9.7.770 is available!

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for Oracle
Locked
Devart
Site Admin
Posts: 3974
Joined: Tue 26 Oct 2004 13:51

New build of dotConnect for Oracle 9.7.770 is available!

Post by Devart » Thu 06 Jun 2019 19:38

Dear users,

New build of dotConnect for Oracle 9.7.770 is available for download now.

In this version:
  • Deprecated design-time Synchronous API calls are no longer used with Visual Studio 2019 and Visual Studio 2017
  • The bug with executing OracleCommand, having CommandType.StoredProcedure, when its CommandText contains a colon, which does not denote a stored procedure overload number, is fixed
  • The bug with processing line breaks by OracleScript, when a script contains lines of only a semicolon character, is fixed
  • The bug with inserting a long string into the VARCHAR2 column on Oracle Server with NLS_CHARACTERSET=UTF8 in the Direct mode is fixed
  • The bug with reading data from the NVARCHAR2 column on Oracle Server with NLS_NCHAR_CHARACTERSET=UTF8 in the Direct mode is fixed
  • The bug with reading CLOB data in the OracleUtils.OracleClientCompatible mode via the reader.GetOracleLob().Value and reader.GetOracleLob().Length properties and reader.GetOracleLob().Read() and reader.GetString() methods is fixed
  • The bug with reading incorrect timestamp's timezone and offset from an Oracle object field when the timezone is presented as a string value, is fixed
  • The bug with throwing "ORA-01000: maximum open cursors exceeded" in the Direct mode is fixed
  • The bug with errors when executing ExecuteArray with large string array parameters without specifying the parameters Size is fixed
LinqConnect (formerly known as LINQ to Oracle)
  • The bug with executing incorrect SQL request (cached during one of the previous calls), when a variable initialized with an empty collection participates in LINQ query, is fixed
Entity Framework support
  • Entity Framework Core 2.2.4 is supported
  • The bug with closing database connection by context.Dispose() in the scope of a distributed transaction in EF Core 2 is fixed
  • The bug with using a value converter, when the .NET data type remains the same, within the WHERE clause in EF Core 2 is fixed
  • The bug with applying an escaped quotation to the idempotent script in EF Core 2 Code-First Migrations is fixed
Devart development team
http://www.devart.com/dotconnect/oracle/

Locked