From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sandro Dentella <sandro.dentella@tin.it>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: TkSql and pg_group...
Date: Sun, 07 Jul 2002 12:34:05 -0400
Message-ID: <8861.1026059645@sss.pgh.pa.us> (raw)
In-Reply-To: <20020707005657.GA23126@bluff.diade.it>
References: <20020707005657.GA23126@bluff.diade.it>
Sandro Dentella <sandro.dentella@tin.it> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, sandro.dentella@tin.it
Subject: Re: TkSql and pg_group...
In-Reply-To: <8861.1026059645@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox