Received: from trends.net (clio.trends.ca [209.47.148.2]) by hub.org (8.9.3/8.9.3) with ESMTP id WAA41789 for ; Tue, 5 Oct 1999 22:13:26 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by trends.net (8.8.8/8.8.8) with ESMTP id TAA28539 for ; Tue, 5 Oct 1999 19:12:05 -0400 (EDT) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id TAA12588; Tue, 5 Oct 1999 19:10:10 -0400 (EDT) To: Herouth Maoz cc: "Mitch Vincent" , pgsql-sql@postgresql.org Subject: Re: [SQL] Reasonable In-reply-to: Your message of Tue, 5 Oct 1999 18:32:03 +0200 Date: Tue, 05 Oct 1999 19:10:10 -0400 Message-ID: <12586.939165010@sss.pgh.pa.us> From: Tom Lane Herouth Maoz writes: > Another potential problem is your use of a six-letter long default for a > varying(1) field ("status"). 6.5.* has some problems with wrong-length default values for char(n) and varchar(n) fields. There is a slightly klugy fix in place for char(n), but a cursory test suggests that it doesn't catch the varchar case. The consequences aren't as bad as they were for char(n): you just get a field value that's longer than it's supposed to be. Workaround: give a correct default value. This is all fixed properly in current sources (6.6/7.0-to-be). regards, tom lane