Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id VAA41424 for ; Wed, 19 Jan 2000 21:20:20 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id VAA18904; Wed, 19 Jan 2000 21:20:09 -0500 (EST) To: "Hamid Khoshnevis" cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] null and integer field In-reply-to: <000601bf62e1$4c1d1040$810a0a0a@emarq> References: <000601bf62e1$4c1d1040$810a0a0a@emarq> Comments: In-reply-to "Hamid Khoshnevis" message dated "Wed, 19 Jan 2000 16:57:17 -0800" Date: Wed, 19 Jan 2000 21:20:09 -0500 Message-ID: <18901.948334809@sss.pgh.pa.us> From: Tom Lane "Hamid Khoshnevis" writes: > The content of an integer field when unassigned appears to be different from > pushing a null into that field. Can someone please explain the difference > and show me how to push an 'unassigned' into that integer field. There is no such concept as 'unassigned' in SQL; whatever you are observing, it's not that. An integer field should indeed be NULL if it hasn't got a default and you didn't provide a value when you inserted the tuple. Can you provide more details about the problem you're having? regards, tom lane