On Thu, 2013-04-18 at 16:52 -0400, Farley Carter wrote:
> It shows it in the sql pane. But when you run it and check the new column
> after it is added then it is a timestamp. I tried it both in pgadmin II and
> running it from sql outside pgadmin.
>
No, I meant all the actions that give you that
Intresting thing. I never thought it is so loose.
On the other side, I would never use double for currency calculations.
It provides instability to results due to floating point precision.
However due to this:
/Thescaleof anumericis the count of decimal digits in the fractional
part, to the r
Dear pg's support and Alexander
Allow me to quote this reference from :
http://www.postgresql.org/docs/9.1/static/datatype-numeric.html
"The type numeric can store numbers with a very large number of digits and
perform calculations exactly. It is especially recommended for storing monetary
a
Try
select (260739.94::double precision * (1.00::double precision /
365.00::double precision) )
default precision in postgres is pretty lossy, use double precision
whenever you need max precision.
2013/4/23 Kanitchet Vaiassava
> **
> *(Bug) Numeric fault calculation*
>
> My company has usi
(Bug) Numeric fault calculation
My company has using postgresql as database for ERP application which in-house
developed.
For store financial and accounting data, we chose "numeric" type for accurate
calculation (and with recommend by postgres's documentation) and we faced the
problem by using
