Re: Update functions and trigger functions by clicking
От | Dave Page |
---|---|
Тема | Re: Update functions and trigger functions by clicking |
Дата | |
Msg-id | BANLkTimvqBr7mpVgdsSFU5EtSxFRhpsbZA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Update functions and trigger functions by clicking (Vinicius Santos <vinicius.santos.lista@gmail.com>) |
Ответы |
Re: Update functions and trigger functions by clicking
|
Список | pgadmin-hackers |
On Sat, Jun 4, 2011 at 8:05 PM, Vinicius Santos <vinicius.santos.lista@gmail.com> wrote: > > Hi, sorry for the delay in responding. > > I agree to share with you. > > First, the update will be different for "F5 refresh" and per "click > refresh". This could confuse people. I don't think so - there's a pretty obvious difference between refreshing the tree on selection of a menu option or button click, and simply refreshing the object that's selected. > Second, this does not obviate the problem of another user to create, for > example, a table and this table does not appear to me. No. it doesn't. > In other words, I think my Schema is completely updated, when in fact it > is not. > > What do you think? Updating the entire schema (it may well be that much, if everything is expanded) is going to be far too expensive on anything but the smallest database on a very fast machine. We have users with schemas ranging from a handful to tens or even hundreds of thousands of objects - for most them, refreshing a whole schema hierarchy on every click is not an option. I'd probably be happy with a patch that offered *both* "refresh object on click" and "refresh object and children on click", but not just the latter - the use case is just too narrow imho. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgadmin-hackers по дате отправления: