From: | jwieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | t-ishii(at)sra(dot)co(dot)jp |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] numeric data type on 6.5 |
Date: | 1999-04-27 10:05:49 |
Message-ID: | m10c4kP-000EBeC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> >> I thought numeric data type on 6.5 allows a very large precision. Am I
> >> missing something?
> >[...]
> >> test=> insert into t1 values(100000000000000000000000000000);
> >> NOTICE: Integer input '100000000000000000000000000000' is out of range; promoted to float
> >
> >Try this.
> >insert into t1 values('100000000000000000000000000000'::numeric);
>
> Thanks. It definitely works!
insert into t1 values('100000000000000000000000000000');
That one too.
The problem is that the yacc parser already tries to convert
it into an integer or float if you omit the quotes. I'll try
to implement a NUMERIC fallback for this case for 6.6 and
then have all the auto conversion functionality so NUMERIC,
INTEGER and FLOAT can be used mixed.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#======================================== jwieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Bitmead | 1999-04-27 10:07:41 | Re: [HACKERS] It would be nice if this could be fixed... |
Previous Message | Tatsuo Ishii | 1999-04-27 09:59:03 | fix for _copyUnique() |