SQLlyCompetitor watch: the SQL editor and keyboard
12 open editor and keyboard issues from five SQL clients, checked against SQLly: phantom lines, triple-bound shortcuts. One bug fixed, two features built.
The SQL editor is where your hands spend their day, and this week it's where the bugs are: phantom line numbers, one chord bound to three things at once, a mouse cursor that forgot it's a cursor, and autocomplete that gives up the moment you write [dbo].[Table]. So I read twelve open editor-and-keyboard issues from Azure Data Studio, Beekeeper Studio, Chat2DB, DBeaver and DbGate, and checked every one against SQLly.
One of them was genuinely ours too β the arrow cursor β and it's fixed today. Two more were feature requests good enough to build on the spot: VS Code-style occurrence highlighting, and an F6 jump between the editor and the results grid (changelog).
This is the daily competitor watch. I take a batch of open issues from other SQL clients' public trackers, check whether SQLly has the same problem, and fix it if it does. The people who reported these did the hard part, so every one of them is named and linked below. Ages are as of October 22, 2026. "Vendor" means someone the tracker marks as a member, collaborator or staff.
The twelve issues
Option to hide or auto-collapse the "Messages" tab after query execution Azure Data Studio #26302
Age: opened 1 year, 5 months ago (May 13, 2025). No vendor reply, ever.
Reactions / comments: 0 / 0.
The vibe: the Messages tab materializes after every PRINT with no close button, no collapse, and no way to stop it. Azure Data Studio was retired in February, so the tab is now permanent, like a tattoo.
Credit: @grcmiguel asked for an off switch.
SQLly: already have it. Server messages sit in a quiet Messages tab that never forces itself open on a routine run, and Cmd+J hides the whole results pane when you want your screen back.
Add "Comment/Uncomment" Functionality as Context Menu Option and Toolbar Button Azure Data Studio #26284
Age: opened 1 year, 6 months ago (April 16, 2025). No vendor reply, ever.
Reactions / comments: 0 / 1.
The vibe: comment toggling exists only as a chord nobody can remember. The lone comment is the reporter following up on their own issue to ask for every Toad and EMS feature while they were at it β can't fault the ambition.
Credit: @Arileth filed it and dreamed bigger.
SQLly: already have it: right-click βΈ Edit βΈ Toggle Line Comment, next to the Cmd+/ (Ctrl+/) shortcut.
BUG/UX: New query tab may show empty lines on open Beekeeper #4715
Age: opened 1 month ago (September 2, 2026).
Reactions / comments: 0 / 1.
The vibe: a contributor confirmed the eleven empty rows aren't content β Ctrl+A stays on line 1; the gutter just draws ghosts to fill the panel. Another contributor replied the same day: "The empty lines are intended." Intended emptiness is a bold design philosophy, and there the matter rests.
Credit: @JeanPaiva42 reported it; @azmy60 declared it a feature.
SQLly: checked β not affected. SQLly's editor renders exactly the lines in the buffer, so a new tab is one empty line, never a screen of ghost gutters.
BUG: Ctrl+L / Cmd+L keybinding conflict between AI Shell, query editor, and table navigation Beekeeper #4699
Age: opened 1 month ago (August 27, 2026). No vendor reply, ever.
Reactions / comments: 0 / 0.
The vibe: the reporter read the config and found ctrlOrCmd+l assigned to three different actions, so the AI shell shortcut loses a fight it's scheduled for three times a day.
Credit: @JeanPaiva42 listed all three bindings.
SQLly: checked β not affected. That chord is bound exactly once in SQLly (the execution-plan viewer), and each keybinding context maps a keystroke to a single action by construction β a three-way tie is not representable.
FEAT: SQL Editor β highlighting a word should highlight that word elsewhere Beekeeper #4781
Age: opened 1 month ago (September 22, 2026).
Reactions / comments: 0 / 0.
The vibe: Beekeeper's founder filed a feature request against his own product with a Sublime Text screenshot as the spec. Founder-filed, zero comments β make of that what you will.
Credit: @rathboma wrote the spec.
SQLly: built today: selecting text softly highlights every other copy of it in the script, VS Code style β on by default, switchable under Settings βΈ Editor βΈ General. See the changelog.
SQL editor mouse cursor remains an arrow instead of changing to text cursor Chat2DB #2790
Age: opened 1 month ago (August 28, 2026).
Reactions / comments: 0 / 2.
The vibe: a bot acknowledged it within the hour; two days later the reporter asked, reasonably, whether anyone had reproduced it. Silence so far. This one stung β when we checked, SQLly had the same papercut: our editor never set a text cursor either.
Credit: @seqwait reported it and asked the follow-up nobody answered.
SQLly: bug β we had it too, fixed today: I-beam over the editor, pointing hand when you hold the navigation key over a table name. Thanks for the nudge. See the changelog.
SQL formatter: line comment scan is quadratic and ignores line endings other than the OS separator DBeaver #42355
Age: opened 13 days ago (October 9, 2026). Closed as fixed October 20.
Reactions / comments: 0 / 1.
The vibe: credit where due: the report includes the offending Java, a complexity analysis, and the fix β the tokenizer copied the rest of the string once per character hunting for the OS line separator β and DBeaver verified and closed it inside two weeks. Fastest vendor response in today's batch by a mile.
Credit: @Hariomlokhande-coder reported it, patch-quality analysis included; mariiachugunova verified the fix.
SQLly: checked β not affected. SQLly's SQL lexer walks forward once, and a pinned test proves line comments end at a bare carriage return, so CRLF, LF, and CR files all tokenize linearly.
SQL templates don't work in the function source editor DBeaver #42262
Age: opened 3 weeks ago (September 30, 2026).
Reactions / comments: 0 / 1.
The vibe: the reporter works on DBeaver β the public tracker doubling as the internal one, the lone comment paging a colleague by handle. Templates work in the main SQL editor but not the function source editor, because two editors means two chances to wire a feature.
Credit: mariiachugunova filed it and paged a colleague.
SQLly: already have it: SQLly has exactly one SQL editor, and its snippets with tab stops work everywhere it appears β there is no second editor to forget.
Autoformat in Value panel not working anymore DBeaver #42248
Age: opened 3 weeks ago (September 29, 2026). Closed as fixed October 21.
Reactions / comments: 0 / 3.
The vibe: the reporter posted a workaround the same day β click a non-JSON cell and come back β the kind of ritual users develop when a format dropdown silently stops formatting. DBeaver traced it to an earlier fix within hours and closed it this week; quick, credit again.
Credit: @nikiromagnoli reported it and found the workaround ritual.
SQLly: already have it: the Cell Details panel renders JSON and XML as an expandable tree automatically β no dropdown to no-op.
BUG: Data Grid Find Column Keyboard Shortcut Not Working DbGate #1208
Age: opened 1 year, 1 month ago (September 24, 2025). No vendor reply, ever.
Reactions / comments: 0 / 0.
The vibe: the cruelest species of shortcut bug: the context menu prints "Find column β Ctrl+F" right beside the item, the chord does nothing, and clicking the item works. The menu is advertising a shortcut that isn't wired.
Credit: @anguyen-901 spotted the dangling shortcut.
SQLly: already have it: Cmd+G opens Go to Column whenever the grid has focus β the same action the header menu and command palette offer, with tests on the dispatch path, because a printed shortcut that doesn't fire is worse than none at all.
FEAT: add keyboard shortcut to jump between Quey and Grid panel DbGate #1498
Age: opened 3 months ago (June 30, 2026). No vendor reply, ever.
Reactions / comments: 0 / 0.
The vibe: the ask: work entirely from the keyboard β write, run, read, fix, rerun β without grabbing the mouse once per lap to get from the grid back to the query. (The typo in the title is the reporter's; the point stands.)
Credit: @opensas asked for the keyboard loop.
SQLly: built today: F6 jumps focus between SQLly's editor and the results grid in both directions, remappable under Settings βΈ Keybindings. See the changelog.
query autocomplete DbGate #1466
Age: opened 5 months ago (May 20, 2026). No vendor reply, ever.
Reactions / comments: 0 / 0.
The vibe: columns are suggested happily after FROM [dbo].Comm2, but write the fully-bracketed [dbo].[Comm2] and the editor goes silent. The reporter apologized for his "rusty english", which had precisely conveyed a bracket-parsing bug.
Credit: @CaveAdsum-Val β Erasmo β pinned it to the brackets.
SQLly: already have it: bracket-quoted dotted prefixes are normalized before completion runs, so columns arrive after [dbo].[Comm2]. exactly as after dbo.Comm2. β with a test standing guard.
That's the editor batch: twelve settled, one shared papercut fixed, two features shipped, and not a single phantom line number on our side. Tomorrow's pile is already waiting.