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?
DateTimeKind for reads is no longer local?
Re: DateTimeKind for reads is no longer local?
Please contact us and specify your email used during registration. We will send the internal build with the fix to that email.
Re: DateTimeKind for reads is no longer local?
Thank @Shalex , confirming the internal build has fixed the issue for us.