Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 5139847591A for ; Sun, 7 Jul 2002 12:34:04 -0400 (EDT) Mailbox-Line: From tgl@sss.pgh.pa.us Sun Jul 7 12:34:04 2002 Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 5966F4758E7 for ; Sun, 7 Jul 2002 12:34:00 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g67GY5Al008862; Sun, 7 Jul 2002 12:34:05 -0400 (EDT) To: Sandro Dentella Cc: pgsql-interfaces@postgresql.org Subject: Re: TkSql and pg_group... In-reply-to: <20020707005657.GA23126@bluff.diade.it> References: <20020707005657.GA23126@bluff.diade.it> Comments: In-reply-to Sandro Dentella message dated "Sun, 07 Jul 2002 02:56:57 +0200" Date: Sun, 07 Jul 2002 12:34:05 -0400 Message-ID: <8861.1026059645@sss.pgh.pa.us> From: Tom Lane X-Spam-Status: No, hits=-5.3 required=5.0 tests=IN_REP_TO,X_NOT_PRESENT version=2.30 X-Spam-Level: X-Archive-Number: 200207/17 X-Sequence-Number: 2826 Sandro Dentella writes: > I'd like to understand how should an editor cope with this case: I'd like > to make tksql able to edit these tables too, but I see no way to act on a > record in a unique way. You should not be editing system catalogs with INSERT/UPDATE/DELETE operations in any case. This points up that the initdb process is pretty lax about marking catalog columns NOT NULL, even though essentially all fixed-width columns in the catalogs are in fact expected to not be null ... regards, tom lane