UniDAC 9.0.1 - PostgreSQL Digit Bug!

[HalilHanBADEM]

Hi,

I sent you a support e-mail and I wanted the developers in the forum to know about it. As a result of my research with a report I received from my users 2 days ago, I saw that there was an error originating from UniDAC or PostgreSQL.

To repeat the error;

* Create a table on your PostgreSQL server. Let there be a float field in the table.
* Enter non-integer values ​​into this float field. For example (0.45; 0.050).
* Connect with Delphi and view the data by querying with Query.
* A long digit number 0.450054054 will appear in the data.

9.x [BUG]
8.4.x [BUG]
8.3.x [WORKING]

I discovered that this error appeared after version 8.3.2 and had to revert to version 8.3.2. It's a big problem for our precision computational app. I am waiting for solution.

Thanks.

[FCS]

Hello,

It may be the PostgreSQL's specific behaviour.

See: https://www.postgresql.org/docs/10/data ... meric.html

They suggest using Numeric type for constant precision.

Regards
M

[HalilHanBADEM]

Hi,

Data (digit count) are not fixed. If it was PostgreSQL behavior, it should react the same way on the data displayed by PgAdmin. In addition, the fact that I get different outputs in UniDAC versions shows that this situation arises from a problem on the UniDAC side.

Regards.

[evgeniym]

Hi guys!
We inform you that we were able to reproduce the issue and fixed it.
This fix will be added to the next build of our product and will be available for all customers.
Kindly note that as temp solution, until new build is not released yet, we can provide you with a nightly build of UniDAC which includes this solution.
To create this build for you, please provide us with your license number and the version of the IDE you are interested in using the contact form https://devart.com/company/contactform.html
You can also use ProtocolVersion = pv20 as a workaround for this problem.

[FCS]

Hello,

Thanks,
When do you plan the next release ?

Regards
M

[evgeniym]

Hi.
The fixed version is planned to be released this month.
However, the time frames may slightly increase.

[HalilHanBADEM]

Hi,

When I tested it with the nightly build, I saw that there was no problem. Problem solved. Thanks for support.

Regards.

[HalilHanBADEM]

Hi again,

I discovered a different problem in the test version and reported it by mail. No problem with ProtocolVersion v20. There is a problem when I set it to v30. Since it is specific to the test version, I only shared the details in the mail.

Regards.

[evgeniym]

Hi there,
We are still waiting for a sample to reproduce the issue, as well as DDL scripts to create and populate test database objects.
Please, provide the needed.

[HalilHanBADEM]

Hi,

I tried to reproduce the problem in a new project tonight but I couldn't reproduce it.
Having this error in my current project may be caused by too many parameters.
There doesn't seem to be a problem for now. If I catch the relevant parameter in my current project, I will contact you again with the relevant resources in the new project.

Regards.

[evgeniym]

Hi!
Ok, sure.
Feel free to contact us any time in case of any questions!
Regards.