Re: [SQL] double precision vs. numeric

2006-08-28 Thread D'Arcy J.M. Cain
On Mon, 28 Aug 2006 16:32:31 +0300 Aarni Ruuhimäki <[EMAIL PROTECTED]> 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 ?

Re: [SQL] double precision vs. numeric

2006-08-28 Thread Michael Fuhr
On Mon, Aug 28, 2006 at 04:32:31PM +0300, Aarni Ruuhimki wrote: > On Monday 28 August 2006 16:08, you 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: > > Ok, th

Re: [SQL] double precision vs. numeric

2006-08-28 Thread Aarni Ruuhimäki
On Monday 28 August 2006 16:08, you 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: > Ok, thanks. But NULLs will go in the future too ? BR, Aarni -- Aarni Ruuhimäk

Re: [SQL] double precision vs. numeric

2006-08-28 Thread Michael Fuhr
On Mon, Aug 28, 2006 at 11:08:50AM +0300, Aarni Ruuhimki wrote: > Now I saw it again. In a terminal window after an insert from an application: > > WARNING: deprecated input syntax for type double precision: "" > DETAIL: This input will be rejected in a future release of PostgreSQL. > > So this

Re: [SQL] double precision vs. numeric

2006-08-28 Thread Aarni Ruuhimäki
On Friday 25 August 2006 08:12, Aarni Ruuhimäki wrote: > On Thursday 24 August 2006 20:29, Tom Lane wrote: > > Aarni =?iso-8859-1?q?Ruuhim=E4ki?= <[EMAIL PROTECTED]> writes: > > > I vaguely remember having seen a message > > > ' ... type double precision ... will be depreciated / unsupported in > >

Re: [SQL] double precision vs. numeric

2006-08-24 Thread Aarni Ruuhimäki
On Thursday 24 August 2006 20:29, Tom Lane wrote: > Aarni =?iso-8859-1?q?Ruuhim=E4ki?= <[EMAIL PROTECTED]> writes: > > I vaguely remember having seen a message > > ' ... type double precision ... will be depreciated / unsupported in > > future releases ... ' > > or something like that somewhere. (?

Re: [SQL] double precision vs. numeric

2006-08-24 Thread Tom Lane
Aarni =?iso-8859-1?q?Ruuhim=E4ki?= <[EMAIL PROTECTED]> 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 PRECI

Re: [SQL] double precision vs. numeric

2006-08-24 Thread Michael Fuhr
On Thu, Aug 24, 2006 at 06:51:33PM +0200, Peter Eisentraut wrote: > Aarni Ruuhimäki wrote: > > ' ... type double precision ... will be depreciated / unsupported in > > future releases ... ' > > That is completely false. Presumably because double precision is standard SQL and has been so for a lon

Re: [SQL] double precision vs. numeric

2006-08-24 Thread Peter Eisentraut
Aarni Ruuhimäki wrote: > ' ... type double precision ... will be depreciated / unsupported in > future releases ... ' That is completely false. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 5: don't forg

[SQL] double precision vs. numeric

2006-08-24 Thread Aarni Ruuhimäki
Hello, Not sure if this is the right list to ask ... I vaguely remember having seen a message ' ... type double precision ... will be depreciated / unsupported in future releases ... ' or something like that somewhere. (?) I have quite a few older dbs with tables that have one or more fields