Hi, Peter Eisentraut <pete...@gmx.net> writes:
> On tis, 2009-09-01 at 11:41 -0700, Josh Berkus wrote: >> Opinions? Other objects which could take \e? > > All of them. Well, I'd vote against \e table. Are you going to propose the CREATE TABLE statement and have magics to produce the ALTER TABLE that would resort? I hope not, because in some cases I fail to see how you'd do it (CREATE TABLE AS SELECT ... comes to mind, and CREATE TABLE ... (LIKE ...) INHERITS ...; too, let alone where to put the column and table constraints: separate commands or embedded ones?). So you'd propose ALTER TABLE ... and nothing more, and I don't see any gain in that, but maybe it's just me. Editing an index is interesting too, do you generate a DROP INDEX then the new CREATE INDEX, do you add a CREATE INDEX CONCURRENTLY somewhere in the mix, etc... More generally, as said upthread, \e should certainly only be available for objects we can CREATE OR REPLACE... Regards, -- dim -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
