New build of dotConnect for Oracle 9.6.597 is available for download now.
In this version:
- The more detailed error text about unsupported data type when working with parameters and when loading data via the OracleLoader class is supported
- Establishing a connection in the Direct mode when the Server connection parameter contains DESCRIPTION_LIST is improved
- The bug with absent Devart.Data.Oracle.NHibernate.NHibernateOracleConnection and Devart.Data.Oracle.NHibernate.NHibernateOracleCommand classes in the .Net Core NuGet package is fixed
- The bug with InitialLobFetchSize not applied when a result set is returned as a cursor from a stored procedure or function or when a SELECT statement returns a nested cursor is fixed
- The bug with freezing when describing a procedure on Oracle 18c is fixed
- The bug with the ORA-64219 error when a CLOB parameter is used in the Direct mode for Oracle 18c is fixed
- The bug with the ORA-01461 error when a LONG parameter is used in the Direct mode for Oracle 12 is fixed
- The bug with the ORA-03106 error when assigning a value to the OracleCommand InitialLobFetchSize property in the Direct mode is fixed
- The bug with the error when reading a char primary key from Oracle 9.2 when the "Unicode=true" connection string parameter is used in the Direct mode is fixed
- The bug with the error when connecting to Oracle 8.1.7 in the Direct mode is fixed
- Using an extended property of type OutputInfo is supported
- Code generated for nullable properties is simplified: now T? is generated instead of System.Nullable<T>
- An additional constructor that accepts DbContextOptions as an argument is added to the DbContext class descendant in the VB.NET version of the DbContext template for EF Core
- The bug with "No database provider has been configured for this DbContext." in the DbContext template for EF Core is fixed
- The bug with code generation for nullable properties for EF1/EF4/EF5/EF6 is fixed
- Entity Framework Core 2.1.3 is supported
- The bug with throwing an error by context.Database.Migrate(), when the __EFMigrationsHistory table already exists but tables being mapped by model classes are not created yet, in EF Core 2 is fixed
- The bug with a memory leak in EF Core 2, when a connection is set for DbContext as an OracleConnection instance, and not via a connection string, is fixed
- The bug with creating database objects in the same schema by several EF Core contexts in Code-First approach is fixed
http://www.devart.com/dotconnect/oracle/