From: D'Arcy J.M. Cain <darcy@druid.net>
To: aarni@kymi.com
Cc: mike@fuhr.org
Cc: pgsql-sql@postgresql.org
Subject: Re: double precision vs. numeric
Date: Mon, 28 Aug 2006 09:49:30 -0400
Message-ID: <20060828094930.54291424.darcy@druid.net> (raw)
In-Reply-To: <200608281632.31039.aarni@kymi.com>
References: <200608241936.50752.aarni@kymi.com>
<200608281108.50394.aarni@kymi.com>
<20060828130827.GB4094@winnie.fuhr.org>
<200608281632.31039.aarni@kymi.com>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: darcy@druid.net, aarni@kymi.com, mike@fuhr.org
Subject: Re: double precision vs. numeric
In-Reply-To: <20060828094930.54291424.darcy@druid.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox