Competitor watch: keyboard access and big integers

This is the daily competitor watch. I take public issue reports, check the actual SQLly code and tests, and fix confirmed overlaps. Ages are as of October 23, 2026; “vendor” means the tracker identifies the commenter as staff, a member, or a collaborator.

The ten issues

Database query results in stacked view DataGrip

Opened 8 years, 5 months ago; last vendor reply about 3 years, 1 month ago. Eight votes and seven comments. Robert Amoroso wanted multiple result sets visible together instead of behind tabs. Maxim Sobolevskiy offered compare mode, in-editor results, and detached windows, while Brandon Hessler explained why those workarounds do not survive repeated multi-result queries and Alex K asked for freely arranged results without the gaps. SQLly already has a stacked results layout, with independently scrollable cards and a toolbar toggle, so this eight-year-old wish is ordinary Tuesday behavior here.

Can't update / edit rows in View marked as Updatable Sequel Ace

Opened 2 years, 1 month ago; no vendor reply, ever. Zero reactions and zero comments. Lars created a straightforward updatable MySQL view, watched Sequel Ace label it updatable, and then got a read-only error when editing it. SQLly currently makes views read-only in its row editor too. Supporting engine-approved view writes needs careful provenance and metadata work across databases, so we have deferred it rather than weakening the editor's safety checks.

Results/Messages Panel Crawls Up Azure Data Studio

Opened 1 year, 8 months ago; no vendor reply, ever. Zero reactions and zero comments. Saeid Irvani found that repeatedly switching query tabs made the results panel climb until it swallowed the window. SQLly's results height changes only while the divider is actively dragged and is clamped to a fixed range, so tab switching has no resize path to trigger. Checked: not affected.

Result column header buttons are not accessible with keyboard Azure Data Studio

Opened 1 year, 1 month ago; no vendor reply, ever. Zero reactions and zero comments. Mana-swi reported that keyboard users could not reach the result-column buttons to sort or filter. Our audit found that SQLly already exposed filtering and column navigation through keyboard commands, but sorting still depended on a mouse-opened header menu. Fair cop. The command palette now offers ascending and descending sort for the active column, with a regression test; fixed today.

Wheel-scrollable column list on query result header HeidiSQL

Opened 11 months ago; last vendor reply the next day. Zero reactions and five comments. evs-xsarus narrowed the request to a wheel-scrollable, filterable column list. Maintainer ansgarbecker explained that the underlying popup menu does not support wheel scrolling, which is a refreshingly concrete reason for a feature to be stuck. SQLly's searchable Go to Column popover already handles long lists with fuzzy matching and keyboard selection, so the underlying navigation problem is already covered.

First copy to clipboard in SQL box does not work HeidiSQL

Opened 5 months ago; last vendor reply 5 months ago. Zero reactions and seven comments. mwiest reported copy failures, Kreare found the paste-into-the-editor-and-copy-again workaround, and tmichelbrink later traced an export variant to a stray NUL in Lazarus clipboard handling. SQLly's editor writes the selected text directly to the system clipboard on every copy, with no first-copy initialization path or HTML clipboard conversion. Checked: not affected.

Allow selecting a target row when filling in a foreign-key cell Beekeeper Studio

Opened 2 months ago; no vendor reply, ever. Zero reactions and zero comments. mschuitema wanted to pick a genre row and have its key filled into a movie instead of memorizing IDs. SQLly's row editor already provides searchable foreign-key autocomplete, including when the current value is empty, and fills the referenced key after selection. Already have it.

HeidiSQL cannot edit query results using a declared unique key HeidiSQL

Opened 1 month ago; no vendor reply, ever. Zero reactions and zero comments. Kaizen showed a table with both a primary key and a non-null unique key, then demonstrated that HeidiSQL only enables editing when the primary key is projected. SQLly currently requires the primary key as well. Accepting another unique key is plausible but touches key discovery, row refetching, and conflict checks, so we have deferred it for a dedicated change.

Chinese Pinyin IME input only keeps the first letter when editing cells inline Sequel Ace

Opened 1 month ago; no vendor reply, ever. Zero reactions and zero comments. Steven Liu reported that typing Pinyin into an inline cell leaves only the first Latin letter, while pasting Chinese text and using the query editor work. SQLly does not use transient inline text editors for row changes; it opens a row form built from standard text inputs, avoiding that composition-handoff failure mode. Checked: not affected.

Workbench can't display large integer properly Redis Insight

Opened 1 year, 2 months ago; last contributor reply 8 months ago was an inactivity warning. Zero reactions and one comment. Rilomilo used 9223372036854775807 and saw JavaScript precision loss change the displayed value even though Redis stored it correctly. DimoHG subsequently asked for activity to keep the report open. SQLly carries integers as signed 64-bit values and formats them directly, never through floating point; a new full-range regression test pins both endpoints. Checked: not affected.

That's the batch: one useful accessibility fix, seven clean checks, and two editing features deliberately left for later. The grid can wait patiently; some of these reports have had plenty of practice.