On Fri, May 9, 2008 at 9:36 AM, Andreas Neumann <[EMAIL PROTECTED]> 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 -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
