X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 669F15666D for ; Thu, 17 Mar 2005 13:57:48 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 41196-03 for ; Thu, 17 Mar 2005 13:57:38 +0000 (GMT) Received: from boutiquenumerique.com (boutiquenumerique.com [82.67.9.10]) by svr1.postgresql.org (Postfix) with ESMTP id EFDF0565CA for ; Thu, 17 Mar 2005 13:57:37 +0000 (GMT) Received: (qmail 24188 invoked from network); 17 Mar 2005 14:57:47 +0100 Received: from unknown (HELO localhost) (boutiquenumerique-lists@192.168.0.4) by boutiquenumerique.com with SMTP; 17 Mar 2005 14:57:47 +0100 To: "Kenneth Gonsalves" , weberp@paradise.net.nz Cc: pgsql-sql@postgresql.org Subject: Re: Query performance problem References: <200503172120.20676.weberp@paradise.net.nz> <200503171801.19412.lawgon@thenilgiris.com> Message-ID: Date: Thu, 17 Mar 2005 14:57:40 +0100 From: PFC Organization: =?iso-8859-15?Q?La_Boutique_Num=E9rique?= Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <200503171801.19412.lawgon@thenilgiris.com> User-Agent: Opera M2/7.54 (Linux, build 955) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.003 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/242 X-Sequence-Number: 20721 > although may be not relevant to your question, as i have noticed this > before with mysql 'sql', what is the point of having a NOT NULL field > that defaults to 0? the whole idea of a NOT NULL field is to have the > value filled in compulsorily and having a default of 0 or '' defeats > the purpose Well if you define your field as NOT NULL mysql will automatically set it to 0 if you store a NULL anyway, so you might as well specify it in your table definitions so it looks like you wanted it...