DateTimeKind for reads is no longer local?

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for PostgreSQL
Post Reply
mpearse
Posts: 9
Joined: Mon 02 Feb 2015 00:00

DateTimeKind for reads is no longer local?

Post by mpearse » Tue 16 Jul 2019 07:05

Hello,

We've just been looking at upgrading to VS2019 and as part of this were upgrading our Dotconnect for Postgresql version to 7.13.1366.

We've noticed what we think is a change when reading datetimetz fields. In Version 7.11.1190 on database reads, the DateTimeKind of any DateTime we read would be Local. Now, the DateTimeKind is returning as Unspecified.

We have not configured PgSqlLocalization.TimeZone, so according to the documentation (https://www.devart.com/dotconnect/postg ... eZone.html )
the previous behavior should still be the case? Hence is this a bug?

We have PostgreSql configured to UTC, the application server set to local time and as noted above have not configured PgSqlLocalization.TimeZone.

Please let me know if you need any other detail?

Shalex
Site Admin
Posts: 9543
Joined: Thu 14 Aug 2008 12:44

Re: DateTimeKind for reads is no longer local?

Post by Shalex » Thu 18 Jul 2019 13:42

Please contact us and specify your email used during registration. We will send the internal build with the fix to that email.

mpearse
Posts: 9
Joined: Mon 02 Feb 2015 00:00

Re: DateTimeKind for reads is no longer local?

Post by mpearse » Tue 23 Jul 2019 03:30

Thank @Shalex , confirming the internal build has fixed the issue for us.

Post Reply