From: | Sergio Lob <Sergio_Lob(at)iwaysoftware(dot)com> |
---|---|
To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org, Ephraim Spravtsev <Ephraim_Spravtsev(at)ibi(dot)com> |
Subject: | Re: Precision and scale of numeric column reported as value |
Date: | 2005-03-23 21:13:22 |
Message-ID: | 4241DBF2.6040807@iwaysoftware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Precision is the number of total digits in the number. Scale is the
number of fractional digits.
For instance, a column defined as NUMERIC(10,3) should return
precision=10, scale=3. The error only occurs for a column defined as
NUMERIC (without precision or scale specified). Presumably, there is a
default precision and scale assigned to the column by postgreSQL, which
is not -1.
Sergio
Oliver Jowett wrote:
> Sergio Lob wrote:
>
>> Bug to report - For a numeric in a table defined by:
>> CREATE TABLE SERG (F01NUM NUMERIC) ;
>> , the precision and scale reported by ResultSetMetaData.getScale() and
>> ResultSetMetaData.getPrecision() are value -1
>
>
> What should they return instead in this case?
>
> -O
>
From | Date | Subject | |
---|---|---|---|
Next Message | Roy Badami | 2005-03-23 21:14:48 | Re: BUG #1518: Conversions to (undocumented) SQL year-month and |
Previous Message | Bruce Momjian | 2005-03-23 21:10:22 | Re: BUG #1518: Conversions to (undocumented) SQL year-month and |