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 ?
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. ---------------------------(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
