Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0BJJhp34470 for ; Thu, 11 Jan 2001 14:19:43 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f0BJJcJ12259; Thu, 11 Jan 2001 14:19:38 -0500 (EST) To: Justin Clift cc: pgsql-sql@postgresql.org Subject: Re: Possible bug? WAS :Bad (null) varchar() external representation. In-reply-to: <3A5CB33B.A2D61F9B@bigpond.net.au> References: <3A5CA5FA.CBDF0513@bigpond.net.au> <3A5CB33B.A2D61F9B@bigpond.net.au> Comments: In-reply-to Justin Clift message dated "Thu, 11 Jan 2001 06:08:43 +1100" Date: Thu, 11 Jan 2001 14:19:38 -0500 Message-ID: <12256.979240778@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200101/109 X-Sequence-Number: 770 Justin Clift writes: > I haven't seen a mention of a maximum number of constraints of similar > applying to a table. If so, then could someone please point me to it... There is no such limit that I know of. > Yet if I remove BOTH the "staff_details_phone_three" & > "staff_details_managers_notes" constraints it works : Are you absolutely certain that that's how it went? I think the most likely story is just that you were hitting the length(varchar)-barfs- on-NULL bug, and got confused about which combinations you'd tried. regards, tom lane