New build of dotConnect for PostgreSQL 7.11.1229 is available!

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

New build of dotConnect for PostgreSQL 7.11.1229 is available!

Post by Devart » Thu 20 Sep 2018 11:42

Dear users,

New build of dotConnect for PostgreSQL 7.11.1229 is available for download now.

In this version:
  • The bug with absent Devart.Data.PostgreSql.NHibernate.NHibernatePgSqlConnection and Devart.Data.PostgreSql.NHibernate.NHibernatePgSqlCommand classes in the .Net Core NuGet package is fixed
LinqConnect (formerly known as LINQ to PostgreSQL)
  • The bug with applying LEFT JOIN LATERAL in the generated SQL is fixed
Entity Developer
  • 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 support
  • 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 PgSqlConnection 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 against PostgreSQL 9.0 and earlier is fixed

Devart development team
http://www.devart.com/dotconnect/postgresql/

Locked