From: Aarni =?iso-8859-1?q?Ruuhim=E4ki?= <aarni@kymi.com>
Reply-To: aarni@kymi.com
Organization: KYMI.com
To: pgsql-sql@postgresql.org
Subject: Re: double precision vs. numeric
Date: Mon, 28 Aug 2006 11:08:50 +0300
User-Agent: KMail/1.6.2
References: <200608241936.50752.aarni@kymi.com>
 <7131.1156440586@sss.pgh.pa.us>
	<200608250812.58794.aarni@kymi.com>
In-Reply-To: <200608250812.58794.aarni@kymi.com>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <200608281108.50394.aarni@kymi.com>

On Friday 25 August 2006 08:12, Aarni Ruuhim=E4ki wrote:
> On Thursday 24 August 2006 20:29, Tom Lane wrote:
> > Aarni =3D?iso-8859-1?q?Ruuhim=3DE4ki?=3D <aarni@kymi.com> writes:
> > > I vaguely remember having seen a message
> > > ' ... type double precision ... will be depreciated / unsupported in
> > > future releases ... '
> > > or something like that somewhere. (?)
> >
> > Perhaps you are thinking of type "money"?  DOUBLE PRECISION is in the
> > SQL standard, it's certainly not going anywhere.
> >
> >    regards, tom lane
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 9: In versions below 8.0, the planner will ignore your desire to
> >        choose an index scan if your joining column's datatypes do not
> >        match
>
> Well, I have used it for 'money type' like sums and prices but I have nev=
er
> used the actual "money" data type.
>
> So, false alarm.
>
> Thank you guys !
>
> Aarni

Hi,

Now I saw it again. In a terminal window after an insert from an applicatio=
n:

WARNING:  deprecated input syntax for type double precision: ""
DETAIL:  This input will be rejected in a future release of PostgreSQL.

So this merely means that in future one can not insert empty values into fi=
eld=20
of type double precision ?=20

BR,

Aarni

=2D-=20
Aarni Ruuhim=E4ki

**Kmail**
**Fedora Core Linux**