Re: double precision vs. numeric - Mailing list pgsql-sql

From D'Arcy J.M. Cain
Subject Re: double precision vs. numeric
Date
Msg-id 20060828094930.54291424.darcy@druid.net
Whole thread Raw
In response to Re: double precision vs. numeric  (Aarni Ruuhimäki <aarni@kymi.com>)
List pgsql-sql
On Mon, 28 Aug 2006 16:32:31 +0300
Aarni Ruuhimäki <aarni@kymi.com> wrote:
> > > So this merely means that in future one can not insert empty values into
> > > field of type double precision ?
> >
> > Right.  8.0 issues a warning and 8.1 gives an error:
>
> But NULLs will go in the future too ?

No, NULL has always been the correct way to insert a non-value into a
field.  Text/char type fields are the only ones where an empty string
is a valid value.

--
D'Arcy J.M. Cain <darcy@druid.net>         |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 425 1212     (DoD#0082)    (eNTP)   |  what's for dinner.


pgsql-sql by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: double precision vs. numeric
Next
From: "Henry Ortega"
Date:
Subject: Trigger on Insert to Update only newly inserted fields?