New build of dotConnect for Oracle 6.70.311 is available!

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

New build of dotConnect for Oracle 6.70.311 is available!

Post by Devart » Mon 27 Feb 2012 12:14

Dear users,

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

In this version:
  • The promoted properties feature of Oracle Workflow Instance Store is implemented
  • The support for BINARY_DOUBLE and BINARY_FLOAT data types in Direct mode is added
  • The behaviour is changed: one internal connection is used now if connections with the same connection string are opened and closed several times in scope of a distributed transaction
  • The bug with CLOB data type in Direct mode, when NLS_CHARACTERSET of a server is set to AL24UTF8, is fixed
  • The bug with Arguments metadata table, that does not contain a row for return value of a function, is fixed
  • The bug with IndexOutOfRangeException on getting zero value using the OracleDataReader.GetByte method is fixed
  • The bug with adding records in ServiceDeploymentsTable of Oracle Workflow Instance Store is fixe
Entity Developer
  • The validation of method parameters in LinqConnect models is added
  • The context menu options for unchecking changed/added/dropped tables are implemented for the root nodes in the "Update To/From Database" wizards
  • The possibility to rename the storage part of the model in Model Explorer is implemented (Entity Framework models)
  • The diagram design is changed: an arrow (instead of a triangle) is used on the tip of an association now
  • The bug with setting comments for columns and tables in database is fixed
  • The bug with adding the MaxLength attribute to the NCLOB properties in SSDL is fixed (Entity Framework models)
  • The bug with adding redundant navigation properties by "Update Model From Database" wizard to the model with TPH inheritance is fixed (Entity Framework models)
Entity Framework support
  • Entity Framework 4.3 (Code First Migrations) is supported
  • The validation of identifier name length in Code-First Migrations is implemented
  • The conversion of .StartsWith, .Contains, .EndsWith to LIKE clause in the generated SQL for the case of expression-based condition is supported
  • The Code-First Migrations behaviour is changed: if the nullable value of the property in migration is not set explicitly, the corresponding column will be created nullable
Devart development team