Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide Drag/Drop and Object Explorer Option in Query Tool Workspace #8293

Closed
anthonydb opened this issue Dec 23, 2024 · 4 comments
Closed
Labels

Comments

@anthonydb
Copy link
Contributor

Describe the solution you'd like

Per #7708 (comment) ...

As a user, I would like to drag and drop table names, column names and other identifiers into a script in the Query Tool workspace. In the current implementation of workspaces, I cannot do this because the Object Explorer is only accessible in its own workspace.

Ideally, in the Query Tool workspace, I would like to have the Object Explorer as a collapsible pane.

Describe alternatives you've considered

  1. I could use the "classic" interface. However, the new workspace layout has been set as the default option, and new users unfamiliar with pgAdmin wouldn't necessarily know they could switch.

  2. I could use autocomplete by pressing CTRL + SPACE. However, doing so generates a list that begins with system items rather than table names in the database, as shown here:

Screenshot 2024-12-23 at 8 53 35 AM

Thus, unless I have some idea of the table name, the autocomplete is not helpful.

@EFrankel-ITEP
Copy link

EFrankel-ITEP commented Feb 6, 2025

+1 this. Workspace mode looks useful, but you gave me the ability to drag in the list of field names and I am not giving that up! 😃

@PtravisCS
Copy link

Another +1 for this. I regularly find myself needing to refer back to the object explorer while writing queries or to copy long table names over. Having the ability to show or hide the explorer from the query pane so I can see it when I need it or have the extra space when I don't would allow me the best of both worlds. Losing this feature is effectively my only complaint about the new UI which seems fine otherwise.

@tonila
Copy link

tonila commented Feb 10, 2025

+1 for object explorer in query tool.

Thankfully I managed to find setting to revert to old layout by going to Preferences > Miscellaneous > User Interface > Layout, and selecting Classic.

95% of my usage of pgAdmin is:

  1. Right click table on Object Explorer -> "View Data"
  2. Modify query via text editor.
  3. Excecute sql

With this new workspace design, I would constantly need to move between tabs to "view data". it doesn't serve my use case very well.

@akshay-joshi
Copy link
Contributor

akshay-joshi commented Feb 11, 2025

Hi All,

Based on feedback from some users regarding the new Workspace layout, we've made a few improvements to the logic. With these changes, the Query Tool and PSQL tabs will now open in the same active workspace where the action is initiated.

For example:

  1. If you're currently working in the default workspace with the Tree view and you open the Query Tool/View/Edit Data or PSQL, it will open within the same workspace.
  2. Similarly, if any action is triggered from the Welcome page for the Query Tool or PSQL, the respective tab will open in the same active workspace.

Additionally, we've introduced a new preference setting: "Open the Query Tool/PSQL in their respective workspaces". By default, this setting is False. If set to True, it will behave like the v9.0 release, where the Query Tool, PSQL, and Schema Diff tabs will open in their respective workspaces when the Workspace layout is used.

We believe this update will provide a more streamlined experience for all users. These changes will be available starting with the v9.1 release scheduled for March 6th. However, if you'd like to try them earlier, you can install the nightly build dated 2025-02-12 or above.

Closing this request as not needed anymore.

@akshay-joshi akshay-joshi closed this as not planned Won't fix, can't repro, duplicate, stale Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants