Re: psql tab completion for updatable foreign tables

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Bernd Helmle <mailings(at)oopsware(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: psql tab completion for updatable foreign tables
Date: 2013-10-18 15:41:33
Message-ID: CA+TgmobOONt-NukjQ5cYPaPRr=FCvOaiir6b2bjUOvMTvrTVYw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 18, 2013 at 1:34 AM, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> wrote:
>> Personally, I think this is too fancy anyway. I'd just complete all
>> views and foreign tables and be done with it. We don't inspect
>> permissions either, for example. This might be too confusing for users.
>
> Yeah, I think you're probably right.

I tend to agree. When the rules were simple (i.e. pretty much nothing
was updateable) it might have made sense to make tab completion hew to
them, but they're complex enough now that I think it no longer does.
There are now three different ways that a view can be updateable
(auto, trigger, rule) and the rules are complex.

Based on that it sounds like we need a new version of this patch. If
that's not going to happen RSN, we should mark this returned with
feedback and it can be resubmitted if and when someone finds the time
to update it.

Thanks,

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-10-18 15:52:36 Re: fdw_private and (List*) handling in FDW API
Previous Message Robert Haas 2013-10-18 15:31:14 Re: Review: Patch to compute Max LSN of Data Pages