On 19 June 2013 18:12, Peter Eisentraut <pete...@gmx.net> wrote: > On 6/19/13 11:50 AM, Dean Rasheed wrote: >> On 19 June 2013 15:22, Peter Eisentraut <pete...@gmx.net> wrote: >>> We still don't have any support for this in psql, do we? >>> >> >> No, but at least we now have an API that psql can use. >> >> There are still a number of questions about the best way to display it in >> psql. >> Should it be another column in \d+'s list of relations? >> Should it appear in \d+ for a single relation? >> Should it distinguish updatable from insertable and deletable? >> Should tab-completion also be modified? >> >> Currently I'm thinking yes, yes, no, yes. > > I would be satisfied with no, yes, no, no. Although I don't know what > tab completion changes you have in mind. >
Yes, on reflection having an extra column in the list of relations is probably not a good idea. In many cases that's just going to be a list of tables, all of which will be updatable. So it would only be for \d+ on a single view or foreign table - simply: Updatable: yes|no Tab-completion was discussed on the original thread, but then I forgot about it: http://www.postgresql.org/message-id/caa-alv4_atxij7paqgvh73n5a0f-patvh5em-lmqu+ofuze...@mail.gmail.com Regards, Dean -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers