Open atulwy opened 9 years ago
Comment #1 originally posted by webyog on 2009-02-17T10:33:42.000Z:
I think there should be a preference for controlling the function of the refresh feature. it would seem to be the most democratic simple way to resolve this issue.
personally, i never work on databases, even remote that are so big i would be anoyed by long waits for a refresh.
the current functionality is very specific. i understand the reasoning behind it, but if you have a specific table selected and hit refresh, i would personally expect at least the tables tree to completely refresh. this isnt what happens currently and only the selected table refreshes.
a global preference to control this setting, if it refreshes specifically in the context of the tree branch or the entire tree would be very useful!
Comment #2 originally posted by webyog on 2012-07-26T11:32:38.000Z:
Another user has asked for Autorefresh in object browser setting in preferences. Refer IB: 117355
"autorefresh at least the left pane object-list in a database when objects are added or deleted or renamed possibly controlled by a preference."
Original issue 992 created by webyog on 2009-02-17T10:28:16.000Z:
From time to time we have to explain to users that the OB refresh option will refresh the currently selected node only.
The problem occur if user create or drop objects by using SQL statements in the editor or by importing external scripts. A 'refresh' is required to load new data into the OB buffer (when using the OB contexst menu's there is no such issue).
Even if 'refresh all' could take considerable time we should consider that option somehow.