Competitor watch: languages, grids and maps

WE NEED CHINESE_T_T — Redis Insight

Opened 1 month, 16 days ago; last vendor reply 1 month, 7 days ago, which said: duplicate, see the other thread. Zero reactions and two comments. return121205-coder wants Chinese, all-caps and crying emoticon included, and a Redis member pointed at the localization umbrella ticket where the exporting work has been in progress since August. hepengju dropped a link to their own third-party client, which is the kind of answer a thread gets while it waits. SQLly ships complete localization today in English and Spanish — same keys, same coverage, checked at build time — and adding Chinese is translation work, not engineering. We looked, decided not to build the Chinese catalog this week, and wrote that down so a future us can reconsider. Declined for now.

Add missing i18n keys to enable full RedisInsight localization — Redis Insight

Opened 2 months, 9 days ago; the vendor replied the same day and hasn't been heard from since. Zero reactions and four comments. itmafia89 offered to keep the localization maintained as the app evolves, a Redis member said the team is "still in the process of exporting the keys", itmafia89 asked to be told when the export finishes, and two months later al6nlee asked "when?". It's a volunteer offering free translation work and waiting on a key export. SQLly's whole UI is catalog-driven — every visible string has an entry, English and Spanish carry identical key sets enforced by the build, and nothing ships half-exported. Already have it.

Add Russian (ru) localization support — Redis Insight

Opened 2 months, 10 days ago; last vendor-side reply 2 months, 10 days ago, and it was a contributor saying please open a PR. Zero reactions and four comments. itmafia89 — the same volunteer — filed the finished Russian PR the same day, registered the locale so it shows up in settings, and the pull request has sat unmerged for over two months. The work is done; it's on a shelf at the warehouse. SQLly's answer is the same as for Chinese: the machinery takes any locale, the English and Spanish catalogs ship today, and a Russian catalog is a task we've parked rather than pretended to have. Deferred.

Upgrade from 3.2.0 to 3.4.1 loses (some of?) the databases — Redis Insight

Opened 6 months, 7 days ago; last vendor reply 5 months, 16 days ago, and it was an apology for having no progress to report. One reaction and five comments. Moulde upgraded and found most of their ten configured databases gone; zainkhan10 hit the same wall on an M1 Pro, asked for updates twice, and got "we don't have much progress 🙁"; StarJiao lost databases imported from an old Mac the same way. The vendor couldn't reproduce it and asked users to go digging in config folders before touching the app again. SQLly's saved connections live in one store written atomically — temp file, fsync, rename — and settings migrations are versioned and run exactly once per file. If the connections file ever fails to parse, SQLly loads nothing, saves nothing over it, and (as of today) tells you so at launch, because your data is in there. While checking we also moved the last preference files that were still written in place over to the same atomic write. Checked, not affected; hardened today.

Version 2.68.0 text of about and upload file is in not readble format in ubuntu 22.04 LTS — Redis Insight

This one is old enough to have started school: opened 1 year, 5 months, 21 days ago; last vendor reply 1 year, 5 months, 20 days ago. Zero reactions and seven comments. abhay-kalariya-scaletech reported the About dialog and upload text rendering as font soup on Ubuntu; KIvanow narrowed it to the snap package in a morning — reproduced it, traced it to snap's font handling, called it outside their control, and ViktarStarastsenka suggested leaving it in the issue tracker for now. It has been sitting in the issue tracker, readable, for seventeen months. SQLly doesn't ship a snap package at all — Linux builds are a plain tarball — so there's no snap font layer to break. Not applicable.

BUG: Alls saved connections gone: Problem loading connections / cannot read properties of undefined — Beekeeper Studio

Opened 2 months, 21 days ago; no vendor reply, unless you count a contributor, which we do: 2 months, 21 days ago. Zero reactions and three comments. abelbraaksma opened the app and every saved connection was gone, and the workaround they found was deleting the App.db file — which they note also loses the session and everything in it. A Beekeeper contributor asked for the corrupted file to reproduce it; abelbraaksma still has it, but it has passwords in it, and they were traveling. So the fix waits on a redacted database from a person on a trip. SQLly's connection store is written atomically, and a store that exists but won't parse is left untouched — never silently treated as empty and clobbered by the next save; there are tests that assert exactly that. Looking closer, we found SQLly kept your file safe but didn't say why the list was empty, so as of today a launch warning names the problem instead of letting you wonder. Checked, not affected; now reported at launch.

Feature: Persist AI Shell chat history between sessions — Beekeeper Studio

Opened 1 month, 24 days ago; no reply, ever — and it was filed by JeanPaiva42, one of their own contributors, which is the database-tool equivalent of leaving a note on the fridge. Zero reactions and zero comments. The ask: AI Shell chats vanish when the app closes; it would be nice if they didn't. We agree, which is convenient, because SQLly already saves every AI conversation to disk — index, full transcripts, search over past chats, delete, and markdown export. Already have it.

Proposal: i18n infrastructure for full UI localization (phase 2 of Swahili support) — Beekeeper Studio

Opened 2 months, 6 days ago; no reply, ever. Zero reactions and zero comments. nyandajr wrote up a phased proposal for the infrastructure needed to localize the whole UI — phase 2 of Swahili support, a sentence that raises plenty of questions nobody has answered. It's a thoughtful, structured plan that has been read by approximately no one with merge rights. SQLly shipped this infrastructure: compiled catalogs resolved with no runtime JSON parsing, per-context keys, host overrides, and a translation workbench on the website where approved wording flows back into the repo through one validated path. Already have it.

Very large scripts get truncated when restarting the application — HeidiSQL

Opened 2 months, 3 days ago; last vendor reply 2 months, 3 days ago. Zero reactions and two comments. frankkaaijk found multi-megabyte scripts cut short after a restart, and maintainer ansgarbecker asked to see the script — which frankkaaijk can't share because it's riddled with sensitive data, so they promised a synthetic reproduction and the thread has been quiet since. A bug that eats your work and can only be chased with a copy of your work. SQLly persists unsaved editor content in the session with no size cap, clamping only labels, paths and parameter values — and as of today there's a test that pushes a two-megabyte script through save and reload and checks it survives to the last line. Checking that, we found the other way to lose it: a session file that couldn't be parsed was quietly replaced by a fresh one. Now it's moved aside with a timestamp and the launch warning tells you where, so your scripts are still on disk. Checked, not affected; hardened today.

External change prompt immediately after saving to Dropbox folder — HeidiSQL

Opened 8 months, 25 days ago; last collaborator reply 5 months, 13 days ago. Zero reactions and two comments. ericgagnaire saved a query into a Dropbox folder and HeidiSQL immediately reported that the file had changed on disk — their own save, reported back to them as news. Ulric-Jessop confirmed it with OneDrive too, and collaborator jonathanp12 confirmed it again on the current build. Three confirmations, including someone with commit access, and the prompt still interrupts every save into a synced folder. We checked, and here we owe HeidiSQL some sympathy: SQLly re-recorded its disk baseline after every save, but compared only the timestamp and size, so a sync client re-stamping the file a moment later would have set off the same prompt. Fixed today: the baseline now carries a hash of the bytes, and a timestamp that moves while the bytes don't stays quiet. Real edits from elsewhere still prompt, same-length ones included. Fixed.

In the latest version 7.2.0, Error messages in Chinese will display garbled characters — DbGate

Opened 4 months, 17 days ago; no reply, ever. Zero reactions and zero comments. WdWangdong reported that server error messages in Chinese arrive as mojibake in the latest release, one sentence, no follow-up, no answer — the shortest report in today's batch and the easiest to lose. SQLly is UTF-8 the whole way through, engine frames included, and as of today there's a test that pushes a Chinese error message through the wire encoding and back and checks it arrives byte-exact. Checked, not affected.

Second batch: the grid, and the values inside it

The afternoon batch is thirty-one reports from six competitors about the two things a database client has to get right: showing a result set, and showing what is inside its cells. An earlier pass had settled most of them on paper; a second, slower read against the code found that a third of those "we already have it" verdicts were too generous. So this half of the day is mostly SQLly owning up: we had nine of these bugs ourselves and fixed them, built eight of the requests (one of them a full map view with heatmaps), and parked three. The other eleven we already had, or checked and don't have.

Highlighting for JSON, XML, Markdown, YAML, etc. in sidebar and data table — Beekeeper Studio

Opened 1 month, 3 days ago by maintainer rathboma, labelled accepted, with a note to keep an eye on performance. No reactions, no comments: a tidy internal ticket waiting for someone to pick it up. SQLly had JSON and XML highlighting in the value viewer but no YAML, no Markdown, and nothing colored inside grid cells. Now it has all three: cautious YAML and Markdown detection with a tree and a rendered preview, and opt-in syntax colors for JSON and XML in the grid that only ever color the visible part of a cell. Built.

Sidebar for values, not only the JSON view — Beekeeper Studio

Opened 1 month, 3 days ago by rathboma, relaying a user with DataGrip envy who wants a value panel that follows the cursor and can be edited. No reactions, no comments. SQLly's Cell Details panel already followed the selection; it could not edit, and it was hard to find (command palette only). Now you can edit in it, the edit is staged like any grid change, and it has a cell-menu entry and a shortcut. Built.

Configure timezone to display timestamp_with_tz columns — Beekeeper Studio

Opened 1 month, 3 days ago by rathboma on behalf of a user whose servers run UTC and whose clients are spread across US zones, a setup they described as "a pain in the asterisk". The ticket asks for global, per-connection and per-table settings. SQLly had the global one. Looking closer, we found a column override silently pinned its column to UTC, and epoch dates ignored the setting altogether. Both are fixed, and columns and connections now get their own zone. Fixed and built.

Styling of geometry in cell viewer — DbGate

Opened 1 month, 11 days ago; no reply, ever. dataspun posted screenshots of the same multipolygon drawn filled one time and hollow the next, and asked why. Six weeks of silence. SQLly's sketch fills every polygon's outer ring the same way, every time, with the type, SRID and bounds next to it. Already have it. It's also on a real map now.

Make fields show their full content beyond a prompt box — DbGate

Opened 4 months, 23 days ago; no reply, ever. LevyQian can only read long values in a tooltip, and said so in one line and a screenshot. SQLly has a resizable Cell Details panel and a full-value viewer that fetches large values on demand. Already have it.

Java object visualization and correct key type detection — DbGate

Opened 6 months, 23 days ago; no reply, ever. ceyhunn keeps Redis Insight open next to DbGate because Java values show empty and every key's type says "none", and pasted Redis Insight's output as the target. SQLly gets key types from Redis itself and summarizes Java serialized values by class, but doesn't decode their fields yet. Deferred: on the list, not built this week.

View BIGINT timestamps as locally formatted dates — Sequel Ace

Opened 2 years, 2 months ago; no reply, ever; one thumbs-up. frumbert is tired of writing queries just to read their own dates. We said we already had this. We had half of it: epoch formatting existed but always rendered in UTC, local setting or not. Fixed, and integer columns named like created_at can now be shown as dates automatically if you switch it on. Fixed and built.

Timezone conversion for datetime fields — Sequel Ace

Opened 1 year, 9 months ago; the only response is a "PR Welcome" label. vuon9 wrote a careful spec: a local-zone setting, a zone picker per column, DST handled properly. SQLly's global conversion was DST-aware; the per-column part wasn't reachable from the settings, and epochs had the bug above. Both fixed today. Fixed and built.

Editing compressed or encrypted BLOBs — Sequel Ace

Opened 2 years, 2 months ago; no maintainer reply, just "PR Welcome". mfichtner asked first; Seemone gzips on the client and compared it to Sequel Ace's UUID decoding; patrickteng called querying the exact row just to read it a hassle. Three friendly people, two years. SQLly decoded gzip, zstd, LZ4 and deflate, but not MySQL's own COMPRESS(), which is the reporter's actual case. Now it does, and you can edit the text and have it packed back exactly as it was stored. Fixed and built; encryption isn't included.

Show values with protobuf with custom .proto files — Redis Insight

Opened 1 year, 10 months ago; no reply, ever; eight thumbs-up and not a single comment, the most-upvoted report in the batch and the quietest. nzapolski wants Kafka-UI-style schema formatters. SQLly showed protobuf by field number; now you can register your .proto files or descriptor sets and read values by field name, remembered per key. Built.

Visualize GEO and GEOSHAPE results in Workbench — Redis Insight

Opened 5 months, 14 days ago. pierrelambert wrote the spec, Redis's valkirilov liked it but warned it was a lot of work, and pierrelambert replied "about to push a PR :)" and did; the PR was merged in May while the issue stays open. Credit where it's due. SQLly now has a map view too: Redis GEO replies, latitude/longitude columns and WKT/WKB shapes on OpenStreetMap tiles you agree to load, heatmaps, and a -- sqlly map: directive to set it all up from the query. Built.

Apache Arrow visualizer — Redis Insight

Opened 1 year, 2 months ago. eugbaranov asked in one line; a stale-bot sweep by DimoHG threatened to close it, eugbaranov said it was still useful, and the reply was "Noted". SQLly has no Arrow viewer either. Deferred.

Small UX Bugs in TableTable — Beekeeper Studio

Opened 22 days ago by maintainer rathboma: an eight-item polish list written while using their own table view, none ticked yet. We first said none of it applied to SQLly. Three of the eight did: the details panel kept showing a row after it was gone, it showed the old value of a cell you'd just edited, and closing a tab threw staged edits away without asking. All three fixed today, plus a transpose bug we tripped over on the way. We had it too, fixed.

Local filtering of data — Beekeeper Studio

Opened 1 month, 3 days ago by rathboma for a user who doesn't want to re-run a slow 20,000-row query just to narrow it. SQLly filters the rows it already has, with quick filters, a visual builder, typed expressions and saved filters. Already have it.

Transpose view for tables — Beekeeper Studio

Opened 1 month, 3 days ago, a Reddit request rathboma called a "dope idea". SQLly has Transpose, keeps your sort and filters, and toggles back. Checking it, we found values shifted one column over while edits were staged; fixed. Already have it.

Data type coloring & color customization — Beekeeper Studio

Opened 1 month, 3 days ago by rathboma: color by type, an off switch, and colors you choose. SQLly had the switch and the type tints but not the choosing. Now each kind gets its own fill and text color. Built.

Order columns — DbGate

Opened 19 days ago. fadhlyz wrote two words; collaborator Stelinkaa asked what they meant, fadhlyz explained (column order in the table designer), the emailed image didn't come through, and fadhlyz patiently posted it again. A week without an answer since. SQLly remembers result-column order but can't reorder a table's columns in the designer. Deferred.

Filters and insertion reject wallet addresses starting with 0x — DbGate

Opened 5 months, 7 days ago; no reply, ever. 0xmask, handle and all, can't filter or insert their own wallet addresses. SQLly's filters and inserts were fine, but its cell menu decided any 0x… text was binary and offered to show it as hex. The menu now goes by the column's type. We had a version of it, fixed.

Message truncates a query print — DbGate

Opened 1 year, 11 days ago, labelled bug; no reply, ever. diecamdia debugs dynamic SQL with PRINT and finds the output cut short. We said SQLly's Messages pane never truncates. True, and beside the point: on SQL Server, SQLly never received PRINT output at all, and PostgreSQL's RAISE NOTICE was dropped too. Worse than truncation, and fixed today. We had it worse, fixed.

Filter and sort by column headers (TTL) — Redis Insight

Opened 1 year, 11 months ago; no reply, ever; three thumbs-up. mooleshacat wants to sort keys by TTL, filter, multi-select and delete. SQLly's key browser is a tree, but SQLLY.KEYS in a query tab returns keys as a grid you can sort and filter by TTL. Now you can also select rows and delete them, set their TTL or remove their expiry. Built.

Custom/multiple delimiters in Top Namespaces — Redis Insight

Opened 9 months, 20 days ago. Eazash explained the use case after Redis's valkirilov asked for one: Telegram-bot keys shaped like Bot_A|user:chat that can't be renamed. Quiet for eight months since. SQLly now breaks memory down by prefix with the delimiters you pick, and the key tree takes more than one. Built.

FT.SEARCH results can't display as a table — Redis Insight

Opened 6 months, 24 days ago, title in Chinese, body an empty template. valkirilov built a full repro and couldn't reproduce it; the reporter, xiangshenb, never came back and the stale label arrived. Real effort on the vendor's side here. SQLly shows FT.SEARCH as one row per document under both Redis reply protocols, with recorded fixtures proving it. Already have it.

Missing Values in Redis Insight 3.2.0 — Redis Insight

Opened 6 months, 18 days ago. The reporter, tanishcb, typed a JSON fragment into the key-name filter and decided the values were gone; valkirilov explained patiently and checked back. No answer. SQLly keeps key filters and value search apart too, but would have shown the same silent empty list, so now it says what's going on and offers to run the search. Not affected, and now it explains.

Configurable or case-insensitive table sort — Sequel Ace

Opened 1 year, 7 months ago. davecarlson has 200 tables, with booking and BookingTimesheet fifty rows apart; maintainer Jason-Morcos suggested a MySQL server setting, which davecarlson can't use. We said SQLly already sorts case-insensitively. Only when the tree came from the cache; a live load kept the server's order. Now both agree. We had it too, fixed.

Option to disable the empty-string indicator — Sequel Ace

Opened 1 year, 11 months ago; no reply, ever. oliveratgithub wrote a neat request; the real annoyance is an inline editor that pre-fills a literal ''. SQLly draws an empty string as blank, keeps NULL distinct, and its editors never invent quotes. Already have it.

Spacing between rows or tables is still reduced — Sequel Ace

Opened 1 year, 7 months ago. salvor-hardin wants the old row spacing back for eyes "that still work at its peak, not mine"; Jason-Morcos liked the idea of a setting, Kaspik pointed at macOS 11, and nexbridge asked them to double it. SQLly has Compact, Normal and Comfortable rows plus its own results font size. Already have it.

Odd output after executing a simple query — Sequel Ace

Opened 1 year, 1 month ago, labelled Cannot Reproduce; no reply, ever. billynoah occasionally gets the table's CREATE TABLE text back from a plain SELECT, the unsettling kind of bug. In SQLly your query takes its own connection out of the pool and metadata reads run on their own, so there's nothing to cross. Checked, not affected.

Filter Apply and Clear buttons are too easy to confuse — HeidiSQL

Opened 1 month, 20 days ago and closed four days ago. rajcz sent a PR; ansgarbecker found it too much code for a small issue and shipped icons instead. Fixed in under two months, which is quick by today's standards. SQLly had the same two quiet buttons; Apply is now the primary one and Clear sits apart. We had it too, fixed.

Paging changes the limit used by other behaviors — HeidiSQL

Opened 11 months, 26 days ago. zsyo paged to a million rows and then every sort ran with LIMIT 1000000; ansgarbecker went from "this is intentionally" to "agreed!" and later moved it out of the milestone, candid about it being a hobby project. SQLly browses with a fixed limit and pages locally; nothing you do changes the next query. Checked, not affected.

Linux cell border style — HeidiSQL

Opened 6 months ago; last reply today. Two collaborators, FingerlessGlov3s and ansgarbecker, have traded screenshots for six months over white dotted Qt lines on KDE, with "Am I blind?" along the way and a new theme color to retest this morning. Very friendly, very persistent. SQLly draws its own solid, theme-colored grid lines on every platform. Checked, not affected.

No single-pointer alternative for column-width dragging — Azure Data Studio

Opened 1 year, 1 month ago; no reply, ever. Mana-swi filed a formal accessibility audit finding against a product that had already been retired, which is one way to get the last word. SQLly had the same gap: dragging was the only way to resize a column. Widen Column and Narrow Column are now in the header's Column menu. Resizing with the keyboard alone is still to come. We had it too, fixed.

That's the afternoon: nine bugs we shared and fixed, eight requests built, eleven we already had or don't have, three parked.