dotConnect for PostgreSQL 7.22 is released!

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

dotConnect for PostgreSQL 7.22 is released!

Post by Devart » Tue 09 Nov 2021 13:30

Dear users,

Devart is glad to announce the release of dotConnect for PostgreSQL 7.22 — a powerful ADO.NET provider for PostgreSQL with advanced support for Entity Framework, Entity Framework Core, LinqConnect (LINQ to PostgreSQL) and NHibernate. The new release offers support for PostgreSQL 14 with its multirange data types and stored procedures with OUT parameters.

Stored Procedures with OUT Parameters

dotConnect for PostgreSQL now fully supports PostgreSQL stored procedures, returning data via OUT parameters.

Multirange Data Type Support

dotConnect for PostgreSQL now supports the following PostgreSQL 14 data types:
  • int4multirange
  • int8multirange
  • nummultirange
  • datemultirange
  • tsmultirange
  • tstzmultirange
We have added the corresponding values to the PgSqlType enum, and the GetProviderSpecificValue method of the PgSqlDataReader class returns an array of the corresponding range objects.

Here is the complete list of dotConnect for PostgreSQL 7.22.2014 changes:
  • The new features of PostgreSQL Server 14 are supported:
    • multirange data types:
      • the database types int4multirange, int8multirange, nummultirange, datemultirange, tsmultirange, tstzmultirange can be used with the provider now
      • the new members IntMultirange, BigIntMultirange, NumericMultirange, TimeStampMultirange, TimeStampTZMultirange, DateMultirange are added to the PgSqlType enum
      • PgSqlReader.GetProviderSpecificValue returns provider-specific range types: PgSqlIntRange[] for int4multirange, PgSqlBigIntRange[] for int8multirange, PgSqlNumericRange[] for nummultirange, PgSqlTimeStampRange[] for datemultirange, PgSqlTimeStampTZRange[] for tsmultirange, PgSqlDateRange[] for tstzmultirange
    • NaN, Infinity, -Infinity values of numeric data types generate a NotSupportedException to avoid inconsistency
    • OUT parameters of stored procedures
  • The start value and the current value of the sequence are saved correctly by PgSqlDump
Entity Developer
  • The bug with parsing discriminator value as string, even when its type is different, in TPH inheritance of EF Core Model is fixed
Entity Framework support
  • Entity Framework Core 5.0.12 is supported
  • Entity Framework Core 3.1.21 is supported
Devart development team
http://www.devart.com/dotconnect/postgresql/

Locked