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 18 Jul 2013 15:43

Dear users,

We are glad to announce the new features that are available in the Entity Framework support in the latest version:
  • Support for spatial data types in Entity Framework 5 and 6 is added (MySQL, PostgreSQL)
  • NetTopologySuite GIS library support in Entity Framework 5 and 6 is added (MySQL, Oracle, PostgreSQL)
  • MySQL spatial 'geometry' data type support in Entity Framework 5 and 6 is added (MySQL)
  • Devart.Data.MySql.Entity.dll assembly built with the 4.5 version of .NET Framework is added (MySQL)
  • The Database value is added to the DeleteDatabaseBehaviour enumeration for creating/removing database, which is specified in the Database connection string parameter, when using CreateDatabase()/DropDatabase() functionality (MySQL)
  • Devart.Data.MySql.Entity.Migrations.dll assembly built with the 5.0 version of EntityFramework.dll is added (MySQL)
  • The MySqlSpatialFunctions class for working with MySQL spatial functions in LINQ to Entities is added (MySQL)
  • PostGIS 'geometry' and 'geography' data type support in Entity Framework 5 and 6 is added (PostgreSQL)
  • Devart.Data.PostgreSql.Entity.dll assembly built with the 4.5 version of .NET Framework is added (PostgreSQL)
  • Devart.Data.PostgreSql.Entity.Migrations.dll assembly built with the 5.0 version of EntityFramework.dll is added (PostgreSQL)
  • The PgSqlSpatialFunctions class for working with PostGIS spatial functions in LINQ to Entities is added (PostgreSQL)
  • The config.SpatialOptions.AlwaysUseGeometryDefaultSrid configuration option (default value is False) is added to provide the possibility to use the config.SpatialOptions.GeometryDefaultSrid value instead of reading the actual SRID for the DbGeometry spatial from the database (MySQL, Oracle, PostgreSQL)
  • The config.SpatialOptions.AlwaysUseGeographyDefaultSrid configuration option (default value is False) is added to provide the possibility to use the config.SpatialOptions.GeographyDefaultSrid value instead of reading the actual SRID for the DbGeometry spatial from the database (MySQL, Oracle, PostgreSQL)
  • The config.Workarounds.UseInvariantProviderManifestToken configuration option (default value is False) is added to provide the possibility of returning the invariant string literal as the provider manifest token (MySQL, Oracle, PostgreSQL, SQLite)
  • The config.SqlFormatting.Identation option is renamed to config.SqlFormatting.Indenting (MySQL, Oracle, PostgreSQL, SQLite)
  • The bug with using delimiter when generating Code-First Migrations script via the ScriptUpdate method of the MigratorScriptingDecorator class in Entity Framework 6 is fixed (MySQL, Oracle, PostgreSQL, SQLite)
Devart development team
http://www.devart.com/dotconnect/entityframework.html
Top
Locked

Return to “Entity Framework support”