New features in the Entity Framework support!

Discussion of open issues, suggestions and bugs regarding Entity Framework support in ADO.NET Data providers
Locked
Devart
Site Admin
Posts: 3974
Joined: Tue 26 Oct 2004 13:51

New features in the Entity Framework support!

Post by Devart » Thu 04 Oct 2012 13:35

Dear users,

We are glad to announce the new features that are available in the Entity Framework support in the latest version:
  • The config.CodeFirstOptions.UseDateTimeAsDate option (default value is False) is added to treat DateTime properties without an explicitly specified server data type as DATE (Oracle)
  • The config.CodeFirstOptions.TruncateLongDefaultNames configuration option (default value is False) is added to provide the possibility of truncating long default names of indexes, primary keys, and foreign keys generated by Code-First Migrations (PostgreSQL)
  • The validation of identifier name length in Code-First Migrations is implemented (PostgreSQL)
  • The bug with setting configuration options via the application config file is fixed (MySQL, Oracle, PostgreSQL, SQLite)
  • The bug with setting the configuration options for Entity Framework v1 is fixed (MySQL, Oracle, PostgreSQL, SQLite)
  • The bug with creating DATE parameters when using LINQ to Entities is fixed (Oracle)
  • The bug with Entity Data Model Wizard/LightSwitch when an access to the objects from the MDSYS schema was required is fixed (Oracle)
  • The bug with demanding extra permissions when running under restricted user account is fixed (Oracle)
  • The bug with generating the "The underlying provider failed on open" error in Entity Data Model Wizard is fixed (Salesforce)
Devart development team
http://www.devart.com/dotconnect/entityframework.html

Locked