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

Bug: in pgAdmin v6.20, double click in search results throws error. #5916

Closed
ecerichter opened this issue Mar 7, 2023 · 7 comments
Closed
Assignees
Milestone

Comments

@ecerichter
Copy link

Describe the bug

I’ve found another little "glitch" in pgAdmin 6.20 regarding search functionality:

1 – search object (of type column)
2 – double click the row (any column)
3 – get the error “Unable to locate this object in the browser.” at bottom of the window

See attached image for reference.

Expected behavior

The the object is selected in browser left pane. Hopefully, user can choose to close or not the search window

Error message

"Unable to locate the object in the browser."

Screenshots

image

Desktop (please complete the following information):

  • OS: docker container
  • Version: 6.20
  • Mode: Server
  • Browser Edge, Chrome, Firefox
  • Package type: docker container

Additional context

nothing else.

@adityatoshniwal
Copy link
Contributor

Found one more related to this. Please check the screenshot. Connected to PG14 server, but on double click it is trying to locate in 9.6
image

@adityatoshniwal
Copy link
Contributor

Hi @ecerichter,

Are you getting the error everytime you open pgAdmin or it goes away after restarting pgAdmin?
I am not able to reproduce it anymore.

Thanks.

@ecerichter
Copy link
Author

ecerichter commented Mar 13, 2023 via email

@ecerichter
Copy link
Author

ecerichter commented Mar 14, 2023 via email

@akshay-joshi
Copy link
Contributor

Closing issue as it is working fine as per the user's response.

@akshay-joshi akshay-joshi closed this as not planned Won't fix, can't repro, duplicate, stale Mar 15, 2023
@akshay-joshi akshay-joshi removed this from the 7.0 milestone Mar 15, 2023
@adityatoshniwal
Copy link
Contributor

Able to reproduce the issue, and fix is available. So re-opening the issue.

@FaharAbbasRizvi
Copy link
Contributor

Tested in the candidate build for v7.0.

akshay-joshi pushed a commit to akshay-joshi/pgadmin4 that referenced this issue Apr 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants