Re: Postgresql problem with update double precision

From: Chris Travers <chris(dot)travers(at)gmail(dot)com>
To:
Cc: condor(at)stz-bg(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: Postgresql problem with update double precision
Date: 2011-08-05 15:26:12
Message-ID: CAKt_Zfsxfjx4fhJ-545Lij1o-LHWOdfsLVfLnH1xUTwCLk1=aQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Aug 5, 2011 at 7:32 AM, Igor Neyman <ineyman(at)perceptron(dot)com> wrote:

> If you want to avoid your problem, switch to NUMERIC(precision, scale), which is precise data type.
> Alter the type of your "double" columns.
>
I'd suggest NUMERIC without specifying precision or scale. That gives
you the most flexibility. I would only specify precision and scale if
these are to be enforced on data input.

Best Wishes,
Chris Travers

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2011-08-05 16:09:55 Re: Is there a better way to unnest an entire row?
Previous Message Tom Lane 2011-08-05 15:16:56 Re: Select count with offset returns nothing.