-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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: Autocomplete wiping whole line #1720
Comments
Hey @mattnSwimd That is very strange. I haven't seen this at all, but I'm going to try and replicate it. Thank you SO MUCH for reporting it. Can you past a SQL query I can use to replicate this behavior? |
Based on where the dropdown appears for the autocomplete in your video it seems like the autocomplete system thinks that |
I cannot post it publicly but a can provide it to you, also I noticed on that same query the Undo and Redo are totally messed up too. Edit: It is an unexpected token causing everything to fail. I attached the error from the dev console. |
Ok that's great. Thanks. If you can find a way to reproduce the problem with a query you can share that would be SUPER helpful. Some other questions to help me debug:
|
My MariaDB version I am currently seeing this in is 10.5.16-MariaDB, for whatever reason I deleted the query by accident and had to retype the part from the video. I restarted to application and now as I am retyping it, the autocomplete is not showing up at all. Sorry this is getting so confusing, I have no idea what is going on with it at this point. Edit: Now I can get the autocomplete open with ctrl+space again. It is still doing the original issue of overwriting the line. |
The error trace you sent me does have a helpful error trace in it. Looks like you're running a pretty complex query and my formatter isn't able to recognize it (It thinks you have a query error). Probably there is something in your SQL code that is confusing the Beekeeper query parsing engine, if it possible to make a generic version of this query to share it would help me identify it. Likely it's a part of the query not shown in the video. Again, any more errors you see in the dev-console will be very helpful in tracking down your errors. Does downgrading to the previous version work ok? |
I haven't tried to downgrade as I am really enjoying this update and even with the issue, I prefer it over the prior version I had. I attached a generic version of the query. I will keep watching for more in the console, and post it here. |
Here is another error I am getting. |
@mattnSwimd In your generic version of the query, can you pinpoint which line that causes the issue? |
It is the second condition on line 47 that caused the issue |
It has just happened again with a totally different query
In this query it happened on the group concat
This is the error it recieved |
@mattnSwimd I've spotted something that potentially is the root cause of this issue and added the patch to this PR #1722. Would you be able to test this using the built files attached on it? Just to confirm from your end. Note: Specifically this line. It needs the |
If you can give me a quick crash course of what you need me to do, I've only worked with the chromium web containers and electron briefly. |
There is a windows executable that you can download at the bottom of the page. This is the link of for the artifact. |
I just ran the second query with that artifact, and it did not mess up on the group concat. I think that change fixes it. |
Thanks @mattnSwimd ! That's great to hear : ) |
Describe the bug
When using the autocomplete for table columns on a left join, it wipes the line for the left join
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should finish typing the selected column name
Screenshots / Gifs
I am attaching a video of it happening
Version Information (please complete the following information):
Windows
4.0.0
Mariadb and mysql
Additional context
Nope
Untitled.mp4
The text was updated successfully, but these errors were encountered: