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

Autocomplete not working after update connection. #7593

Closed
anilsahoo20 opened this issue Jun 18, 2024 · 4 comments
Closed

Autocomplete not working after update connection. #7593

anilsahoo20 opened this issue Jun 18, 2024 · 4 comments
Assignees
Milestone

Comments

@anilsahoo20
Copy link
Contributor

Please note that security bugs or issues should be reported to [email protected].

Describe the bug

When we update the connection from one database to other database, the autocomplete is not working.

To Reproduce

Steps to reproduce the behavior:

  1. Open query tool
  2. Type something, autocomplete will work
  3. Now update the connection
  4. try typing something
  5. autocomplete not working

Expected behavior

It should work.

Error message

data: null
errormsg: "Transaction ID not found in the session."
info: "DATAGRID_TRANSACTION_REQUIRED"
result: null
success: 0

Screenshots

If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: OSX Ventura
  • Version: 8.8
  • Mode: Desktop
  • Browser (if running in server mode): [e.g. chrome, safari]
  • Package type: [e.g. RPM, DEB, Python, Container, etc.]

Additional context

Add any other context about the problem here.

@pravesh-sharma
Copy link
Contributor

Found below issue:

If autocomplete is off and ctrl+space is used to trigger autocomplete it can not be done after updating the connection.
If autocomplete is enabled in that case everything works fine.

@adityatoshniwal
Copy link
Contributor

Hi @pravesh-sharma,
I checked again and API is being called with correct txn id, which was fixed.

@pravesh-sharma
Copy link
Contributor

Hi @pravesh-sharma, I checked again and API is being called with correct txn id, which was fixed.

Okay. What I mentioned seems to be another issue will create a separate one for it.

@pravesh-sharma
Copy link
Contributor

Issue fixed. Tested on snapshot build.

Env:
OS - macOS Sonoma 14.5
Mode - Desktop

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