Skip site navigation (1) Skip section navigation (2)

Re: Editing Views with EditGrid

From: "Dave Page" <dpage(at)pgadmin(dot)org>
To: "Andreas Neumann" <a(dot)neumann(at)carto(dot)net>
Cc: pgadmin-support(at)postgresql(dot)org
Subject: Re: Editing Views with EditGrid
Date: 2008-05-12 08:09:01
Message-ID: 937d27e10805120109t6b09cf24u84fb3ddaca7b0299@mail.gmail.com (view raw or flat)
Thread:
Lists: pgadmin-support
On Fri, May 9, 2008 at 9:36 AM, Andreas Neumann <a(dot)neumann(at)carto(dot)net> wrote:
> Hi Dave,
>
>  You are right about the complexity of rules and triggers. But isn't that
> the same with tables as well?

That's true, but is quite rare. With views the problem is almost
always lurking just around the corner.

>  I don't have a clean and easy solution as well. But one might think about a
> GUI where one lets the user editing the table or view decide whether he
> wants to reload the current record or the whole table/view after each edit.
> Per default it wouldn't update, but if the user enables updating of the just
> edited record or reloading the whole table/view it would.

Technically thats possible of course, but I can see it leading to
false bug reports because people forget, or don't realise such options
exist.

>  Regarding the views: one could test if the view has at least the insert,
> update and delete rules present before enabling the editing of the views.

That goes without saying.

-- 
Dave Page
EnterpriseDB UK:   http://www.enterprisedb.com

In response to

pgadmin-support by date

Next:From: Dave PageDate: 2008-05-12 08:16:02
Subject: Re: Can't get the debugger going
Previous:From: William GarrisonDate: 2008-05-09 16:10:50
Subject: Can't get the debugger going

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group