Auto refresh of Object Explorer on when updating objects

[bjorngback]

When I update something from the Object Explorer, e.g. if I open a table and change a column name, the Object Explorer still shows the old object. To get it updated I need to right click and select refresh.

Obviously it is pretty annoying to do this every time if I want to be sure that the Object Explorer is showing the correct information. I therefore suggest the improvement that when one clicks save after having updated an object, it does an automatic refresh of the Object Explorer (i.e. it automatically triggers the same refresh I get by doing right click -> refresh).

[adityatoshniwal]

pgAdmin should auto-refresh in that case. Its a bug if it is not.

[khushboovashi]

The child node is not getting updated if it is updated from the parent node in the object explorer.

[anthonydb]

I was just coming here to ask about this. It would also be good if the Object Explorer automatically refreshed every time a CREATE DATABASE or CREATE TABLE statement is executed.

[adityatoshniwal]

I was just coming here to ask about this. It would also be good if the Object Explorer automatically refreshed every time a CREATE DATABASE or CREATE TABLE statement is executed.

The problem is how do we detect that a new database or table is created.

[khushboovashi]

I was just coming here to ask about this. It would also be good if the Object Explorer automatically refreshed every time a CREATE DATABASE or CREATE TABLE statement is executed.

Did you mean, whenever the CREATE DATABASE or CREATE TABLE executes from the Query Tool?

[anthonydb]

@khushboovashi
Yes, when I execute CREATE DATABASE or CREATE TABLE in the Query Tool.

I wouldn't expect pgAdmin to know about those commands run outside the tool, e.g. in psql.

[khushboovashi]

@khushboovashi Yes, when I execute CREATE DATABASE or CREATE TABLE in the Query Tool.

In that case, we need to manage DELETE, UPDATE statements too.

I wouldn't expect pgAdmin to know about those commands run outside the tool, e.g. in psql.

[anthonydb]

In that case, we need to manage DELETE, UPDATE statements too.

Yes, that makes sense! I hope it is possible to implement that feature.

[pravesh-sharma]

Hi @anthonydb,

You can submit a new feature request for it.

[pravesh-sharma]

Tested the issue and it is working fine.

[anthonydb]

@pravesh-sharma
Feature request created at #8250