Currency field shows zero instead 1000 or more in russian locale

The forum for ZeosLib 7.2 Report problems. Ask for help, post proposals for the new version and Zeoslib 7.2 features here. This is a forum that will be edited once the 7.2.x version goes into RC/stable!!

My personal intention for 7.2 is to speed up the internals as optimal a possible for all IDE's. Hope you can help?! Have fun with testing 7.2
Post Reply
dpetinov
Fresh Boarder
Fresh Boarder
Posts: 7
Joined: 26.10.2014, 18:05

Currency field shows zero instead 1000 or more in russian locale

Post by dpetinov »

Using 7.2.5 rc, PostgresPro 10 on Linux x64 in Lazarus.
Currency field shows zero when becoming 1000 and more.

Other Clients (SQLDB, jdbc) shows money normally
Not sure is that because of locale or not.
dpetinov
Fresh Boarder
Fresh Boarder
Posts: 7
Joined: 26.10.2014, 18:05

Re: Currency field shows zero instead 1000 or more in russian locale

Post by dpetinov »

Forry for the desinformation. SQLDB shows the same behaviour.
It's a problem of lazarus or freepascal may be
dpetinov
Fresh Boarder
Fresh Boarder
Posts: 7
Joined: 26.10.2014, 18:05

Re: Currency field shows zero instead 1000 or more in russian locale

Post by dpetinov »

Sorry again. Now checked SQLDB correctly - it shows bad symbols instead of space in russian locale money (separator between thousands and below)
but not zero as zeos does! It seems SQLDB more correct than zeos 7.2.5 rc...
marsupilami
Platinum Boarder
Platinum Boarder
Posts: 1962
Joined: 17.01.2011, 14:17

Re: Currency field shows zero instead 1000 or more in russian locale

Post by marsupilami »

Hmmm - which field type do you use in the database? We would need like a correct test case.
dpetinov
Fresh Boarder
Fresh Boarder
Posts: 7
Joined: 26.10.2014, 18:05

Re: Currency field shows zero instead 1000 or more in russian locale

Post by dpetinov »

in postgres this type called money
dpetinov
Fresh Boarder
Fresh Boarder
Posts: 7
Joined: 26.10.2014, 18:05

Re: Currency field shows zero instead 1000 or more in russian locale

Post by dpetinov »

Besides, when in SQL select I cast it to numeric(10,2) in zeos it becomes float and shows correct value.
Then, hacking fieldtype to currency solves the poblem - but this is a hack of cause.
Post Reply