Version 6.3.12 & PostgreSQL & TIMESTAMP

[Bert1234]

With version 6.3.12, when I set a DateTime value using a TUniTable component, the millisecond part of the value is always 0 in the table.
I have tested with PostgreSQL 9.5.2.

After downgrading to 6.2.10 everything is okay again.

[azyk]

We can't reproduce the described problem on the latest UniDAC version. Please try to compose a small sample reproducing the isuue and send it to andreyz*devart*com. Using the pg_dump standard utility, create a test database dump, on which the issue is reproduced and include the dump to the sample.

In addition, let us know Windows regional settings on the client machine. For this, open in explorer Control Panel\Clock, Language, and Region , click Region, let us know the value of the Format checkbox on the Formats tab. Switch to the Administrative tab and let us know the value of the 'Current language for non-Unicode programs:' option.

[azyk]

We have reproduced the issue using your sample. It is most likely related not to UniDAC version, but to PostgreSQL 9.5.2 specificities, since we have checked UniDAC 6.3.12 functioning on servers 9.5.0 and 9.5.1 and haven't detected this issue. We are currently investigating the issue and we'll inform you about the results.

[Bert1234]

What is the status of this issue?
Two weeks have passed since the last message and since then PostgreSQL 9.5.3 has been released. Has it been fixed in this version?

[MaximG]

We continue investigation of the issue when working with TimeStamp fields. We are checking the behavior of UniDAC on different versions of PostgreSQL , including the PostgreSQL version 9.5.3. We will inform you about the results shortly.

[MaximG]

We have already fixed the error, and the fix will be included in the next build. We plan to release the build next week.