Big results in the browser no longer eat the tab
SQLly's browser version now keeps big query results in browser storage (OPFS) instead of memory, so a million-row result scrolls, pivots and stays light.
Read the post →Long-form write-ups on how SQLly works and why it works that way: the guardrails, the plumbing, and the small comforts that make a SQL client pleasant to live in. Every claim here is checked against the docs and the changelog, and anything unfinished is labelled as such.
SQLly's browser version now keeps big query results in browser storage (OPFS) instead of memory, so a million-row result scrolls, pivots and stays light.
Read the post →SQLly 應用程式與網站現在提供繁體中文。從「設定 → 外觀 → 語言」就能套用,網站上也有語言選單。第一版是機器輔助翻譯,用詞難免不自然,歡迎從「說明 → 傳送意見回饋」告訴我。
Read the post →SQLly 应用和网站现已支持简体中文。设置里可以切换应用语言,网站顶部的语言选择器也能把公开页面、文档和工具换成中文。第一版是机器辅助翻译,用词难免不自然,欢迎从应用里直接反馈。
Read the post →Use o SQLly e o site em português do Brasil. A primeira tradução teve ajuda de máquina, e você pode mandar correções pelo app.
Read the post →SQLlyのアプリとウェブサイトを日本語で使えるようになりました。言語の切り替え方法と日本語になる範囲、最初の機械翻訳版の限界、フィードバックの送り方を紹介します。
Read the post →SQLly 앱과 웹사이트에서 한국어를 사용할 수 있습니다. 언어 설정 방법과 한국어가 적용되는 범위를 소개합니다. 첫 기계 번역 검토본이라 어색한 표현은 앱의 피드백 메뉴로 알려 주세요.
Read the post →Русский язык появился в приложении SQLly и на сайте. Рассказываю, как включить его, где он работает и как помочь мне улучшить формулировки.
Read the post →SQLly ist jetzt auf Deutsch verfügbar – in der App und auf der Website. So aktivierst du die Sprache und meldest Formulierungen, die noch nicht passen.
Read the post →SQLly est disponible en français dans l’app et sur le site. Voici comment changer de langue et me signaler les formulations à retravailler.
Read the post →The SQLly editor now autocompletes -- sqlly directives: every directive, setting and value, plus your real column names quoted the way each one needs.
Read the post →SQLly charts used to read the first 10,000 rows. Now sums, histograms and line charts use every row, even of results spilled to disk, spikes included.
Read the post →SQLly's Pivot tab used to lock on results spilled to disk. Now it pivots every row of a million-row result in the background, with drill-through.
Read the post →How I prototyped spilling huge query results to OPFS in SQLly's browser build: why not localStorage, a tiny worker, real numbers, and what's left.
Read the post →I build SQLly, so I'm biased. How DbSchema's diagrams, HTML5 docs, schema sync and Git compare with SQLly, what each costs, and when to pick DbSchema.
Read the post →I build SQLly, so I'm biased. How the hosted, team-focused SaturnSQL compares on engines, sharing, schedules, result limits, safety and cost, and when to pick it.
Read the post →Basevolt is an Electron admin panel with kanban, dashboards, webhooks and MCP. Here's how it compares to SQLly on engines, SQL, safety and cost.
Read the post →I build SQLly, so I'm biased. Here's how Peek's infinite-canvas, FK-clicking, multiplayer Mac client compares on engines, safety, AI and cost.
Read the post →I build SQLly, so I'm biased. Here's how it stacks up against Valentina Studio on engines, reports and forms, Free vs Pro limits, safety and price.
Read the post →I build SQLly, so I'm biased. Here's how Tablething, a $49 Tauri database client with 31 sources and BYOK AI, compares on engines, AI, dashboards and price.
Read the post →I build SQLly, so I'm biased. Rustable is a free MIT client on egui; SQLly is on GPUI. Engines, safety, result limits, Redis, cost, and who should pick which.
Read the post →I build SQLly, so I'm biased. Here's how the free, MIT-licensed Antares SQL compares on engines, size, editing, safety, cost and upkeep, and when to pick it.
Read the post →Klyndb is a free MIT Tauri client in early preview with MongoDB and Redis. Here's how it compares to SQLly on engines, editing, plans, platforms and cost.
Read the post →Write WHERE id = :id, type 42, press Run. SQLly now fills in :name, ? and $1 placeholders on every engine, because one user told us it was broken.
Read the post →SQLly 1.31.0 cut scroll CPU by caching parts of the window, and made typing 80 to 120 ms late. What broke, why, and what 1.34.2 fixes.
Read the post →Why I check other SQL clients' bug reports against SQLly, turn them into tests, and email the reporters a free lifetime license. Yes, it's self-promotion.
Read the post →SQLly now syncs saved connections, snippets, queries and settings between your Macs through your own iCloud Drive. Off by default; passwords stay put.
Read the post →Every open issue at Gridex, Chat2DB and Sequel Ace, checked against SQLly: one shared bug fixed, two of our own found, fourteen requests built.
Read the post →Free SQL formatter with pages for T-SQL, PostgreSQL, MySQL, SQLite, Oracle, Snowflake, BigQuery and Redshift, plus minify, a change report and every app setting.
Read the post →Build or decode connection strings for 10 engines in every driver format, with warnings about TLS, passwords and typos. Nothing leaves your browser.
Read the post →A searchable reference of 611 SQL Server, PostgreSQL, MySQL, SQLite and Oracle error codes, with causes, fixes and safe repro scripts.
Read the post →Paste a SQL Server, PostgreSQL, MySQL, MariaDB, SQLite, DuckDB, ClickHouse or Oracle plan and get ranked findings, a tree and a diagram. Runs in your browser.
Read the post →Students, teachers and researchers with a school email get every paid SQLly desktop feature free, one install at a time, renewed yearly by verifying again.
Read the post →After setting up AI projects for many friends, I built dreamitbuildit.ai: test and live sites, a database, AI credits, a domain, email and secure uploads. 3-day free trial.
Read the post →How we profiled SQLly's results grid on an M4 Max MacBook Pro and cut scroll CPU from about 36% of a core to 28%, or 22% with a new 60 per second repaint cap.
Read the post →An honest look at lazysql, the MIT-licensed Go terminal UI inspired by lazygit, next to SQLly: engines, footprint, SSH, editing, safety, and who should pick which.
Read the post →rainfrog is an MIT-licensed Rust TUI with vim keys that runs over SSH; SQLly is a GPU-drawn desktop workbench with SQL Server, deep IntelliSense and DBA tools.
Read the post →gobang is a small MIT-licensed Rust TUI for MySQL, PostgreSQL and SQLite that has not shipped since 2021; SQLly is a desktop SQL workbench. Where each one fits.
Read the post →An honest look at DataZen, the free GPL database client built with Tauri and Rust: download sizes, engines, workflows, MCP write modes, and where it beats SQLly.
Read the post →Harlequin is a free, MIT-licensed SQL IDE that runs in your terminal; SQLly is a GPU-drawn desktop workbench. Adapters, SSH, results, agents and price, compared.
Read the post →After a family Disney cruise I'm back on SQLly. On the trip I read through Tusk and DBDelve, two other Rust GPUI database clients, and both have ideas worth checking out.
Read the post →DBDelve and SQLly share a UI framework and most of their driver crates. Where they differ: blocking vs async drivers, engines, ODBC, guardrails, DBA tools and price.
Read the post →Tablio is a free MIT Tauri client with Cassandra support and careful grid editing; SQLly goes deeper on SQL, guardrails and tools. An honest side-by-side.
Read the post →Tusk and SQLly are both Rust apps drawn by GPUI. Tusk goes wide on engines and keyboard flow; SQLly goes deep on SQL, results and guardrails. Here's where each one wins.
Read the post →WhoDB is an Apache-2.0 Go server you open in a browser, with MongoDB and Elasticsearch; SQLly is a native Rust workbench with SQL Server, Oracle and deep SQL tooling. Where each one wins.
Read the post →DBine is a free Apache-2.0 Tauri client listing 130+ engines, a profiler, migration, sync and a phone app. What the engine count means, where it beats SQLly, and where SQLly goes deeper.
Read the post →An honest look at dbForge Studio for SQL Server next to SQLly: editions and prices, Windows-only vs native on three OSes, where dbForge's depth wins, and where SQLly differs.
Read the post →TablePro is an AGPL Swift app for Mac, iPhone and iPad with 37 engines, AI and MCP; SQLly is one Rust workbench for macOS, Windows and Linux. Platforms, engines, plans, safety, agents and price, compared.
Read the post →An honest comparison of DB Pro and SQLly: download sizes, engines, free-plan limits, dashboards, AI, the self-hosted Studio, and who should pick which.
Read the post →SQLly's desktop source is coming to GitHub under PolyForm Small Business. What source available means, how it differs from open source, and the plan to open the client.
Read the post →Import and export connections for pgAdmin, Azure Data Studio, VS Code, DBeaver, DataGrip, DbGate and pg_service.conf, plus Jupyter notebooks and VS Code snippets.
Read the post →Gridex is three native apps built around AI chat and MCP; SQLly is one Rust workbench built around SQL. Engines, agents, safety, tools and price, compared.
Read the post →DBX's macOS download is 45 MB and SQLly's is 66 MB, though both are Rust. Where the megabytes go, what it means for speed, and which features each one bets on.
Read the post →Tabularis keeps three drivers and plugins for the rest; SQLly builds thirty engines in. An honest look at notebooks, web mode, admin tools and price.
Read the post →All 117 open DataGrip issues on our watch list checked against SQLly: one shared bug fixed, twelve features built, and the rest checked and explained.
Read the post →Forty-two competitor reports checked against SQLly: localization and saved state, then results grids and cell values. Ten bugs we shared, fixed; eight requests built.
Read the post →Twelve Redis Insight, DbGate and Chat2DB reports on clusters, Sentinel and restricted users checked against SQLly: one bug fixed, two features built.
Read the post →SQLly now draws any result with locations on a street map: Redis GEO, lat/lon columns and PostGIS shapes, with heatmaps and a -- sqlly map: directive to save it.
Read the post →Twelve schema-tree and metadata reports checked against SQLly: a CREATE TABLE refresh gap fixed, a SQLite bug found and fixed, column filter and schema hiding built.
Read the post →23 keyboard, import, export and backup issues checked against SQLly: existing coverage verified, empty filenames guarded, and broader features deferred.
Read the post →10 results-grid issues checked against SQLly: keyboard sorting fixed, stacked results and foreign-key selection covered, large integers verified exact.
Read the post →A 0.5 MB SQL import made SQLly's editor take 0.7 s per keystroke. A loop that re-read the script once per statement was quadratic; now one pass takes 5 ms.
Read the post →12 open connection, auth and SSL issues from seven SQL clients checked against SQLly: Kerberos packaging, master passwords, rotating certs, idle tunnels.
Read the post →12 open editor and keyboard issues from five SQL clients, checked against SQLly: phantom lines, triple-bound shortcuts. One bug fixed, two features built.
Read the post →12 open results-grid issues from five SQL clients, checked against SQLly: stuck column widths, scrollbar traps, an 11-year-old request. One is now a setting.
Read the post →12 open crash and freeze reports from six SQL clients, checked against SQLly: launch hangs, frozen grids, tab crashes, and one latent crash of ours, fixed.
Read the post →Type an Excel formula on any SQL result: colored references, running totals and dates, saved in the query and exported to Excel as live formulas.
Read the post →SQLly already auto-sizes and remembers columns. Now one click writes widths, order, sort, filters and colors into the query, so the grid travels with it.
Read the post →SQLly reads plain-language dates in a WHERE clause and writes the exact literal or BETWEEN range for your column, then keeps saved queries current in one click.
Read the post →12 open font and display issues from five SQL clients, checked against SQLly: stuck sizes, blurry grids, light boxes in dark mode. Two were ours, fixed.
Read the post →I checked 12 open issues from four SQL clients where valid SQL gets flagged as an error: PostgreSQL 17, JSON_TABLE, PIVOT. Two were SQLly bugs, fixed today.
Read the post →I checked 12 open issues about huge cells and binary keys from five SQL clients against SQLly. Two were ours, both fixed today, plus one more found on the way.
Read the post →I checked 12 open connection issues from six SQL clients against SQLly: idle drops, stuck cancels, SSH tunnels. Four were SQLly bugs, all fixed today.
Read the post →I checked 12 open connection bugs from DBeaver, Sequel Ace, Beekeeper, DbGate, HeidiSQL and Azure Data Studio against SQLly. Three were ours; all are fixed.
Read the post →Twelve open issues from DBeaver, DataGrip, HeidiSQL, Sequel Ace, DbGate and Beekeeper on parameters, script splitting and autocomplete, checked against SQLly.
Read the post →I checked 12 open DDL-script bugs from DBeaver, DataGrip, HeidiSQL and DbGate against SQLly. Seven were ours; all are fixed, plus one new feature.
Read the post →Why a Redis connection fails, step by step: DNS, SSH tunnel, TCP, TLS, AUTH, RESP3, SELECT. Plus command timeouts, SSH keepalives and OS trust roots.
Read the post →Redis consumer groups in SQLly, hands-on: spot a dead consumer by lag and idle time, then XAUTOCLAIM, XACK, XCLAIM and trim, exact command shown first.
Read the post →Redis completion that reads the server's COMMAND DOCS: fitting options, subcommands, key names, and hover cards with Write and Destructive badges.
Read the post →How SQLly follows a Redis Sentinel failover: reads re-resolve the master and retry once; write scripts stop with master changed, so nothing runs twice.
Read the post →How SQLly routes Redis Cluster commands by slot, rewrites announced node addresses with a node map, and opens per-node SSH forwards behind a bastion.
Read the post →Redis in SQLly now edits keys by type, shows stream consumer groups, completes commands, and connects to Cluster, Sentinel and Azure Redis with Entra.
Read the post →How SQLly's Redis key view pages, edits and decodes values without turning 00014 into 14: exact commands first, KEEPTTL, hex edits, codecs and live tests.
Read the post →Get SQLly from the Mac App Store: free with 2 connections, a one-time purchase for unlimited, and why it always trails the download by a few versions.
Read the post →12 open results-grid bugs from DBeaver, DataGrip, Beekeeper, DbGate, HeidiSQL, Sequel Ace and Azure Data Studio, checked against SQLly. Two were ours.
Read the post →Staging and production drifted again. Here's how to compare two database schemas with plain SQL queries you can run anywhere — no special tooling needed.
Read the post →Thinking of leaving DataGrip? What a native, one-time-price SQL client does differently: speed, guardrails, no account wall — and when DataGrip still wins.
Read the post →Why a Java-based SQL client can freeze on large datasets, what a native Rust engine does differently, and how to test both on your own queries before switching.
Read the post →Embed a SQL editor in your web app the right way: credentials stay server-side, safety limits are built in, and users get a full workbench. Working code inside.
Read the post →An accountant exported journals to Excel every week just to pivot them. We built pivots and charts into the results so he could stop. He dropped Excel entirely.
Read the post →A practical DBeaver migration guide: autocomplete accuracy, big-result performance, guardrails, and yearly subscriptions versus one-time pricing.
Read the post →SQLly Embedded launches can now open query tabs with the script, connection, parameter values and cursor set. How to build an Open in SQLly button.
Read the post →How testers, analysts and accountants moved from SQL logins in Azure Data Studio, SSMS, DataGrip and VS Code to querying through SQLly, no credentials.
Read the post →Connect a desktop SQL client to Turso or self-hosted libSQL: libsql:// URLs, auth tokens, transactions over HTTP, large results and embedded replicas.
Read the post →EXPLAIN, EXPLAIN ANALYZE, SHOWPLAN_XML and EXPLAIN QUERY PLAN side by side: which ones run your query, and what to look for in any plan.
Read the post →Azure Data Studio was retired on February 28, 2026. An honest guide to the replacements: VS Code with MSSQL, SSMS, and native clients like SQLly.
Read the post →SQLly directives are plain SQL comments that pivot, chart, format and lay out your results, so the presentation travels with the .sql file.
Read the post →Run SQL straight against Parquet and CSV files with DuckDB: read_parquet, read_csv, globs, SUMMARIZE, views over files, and exporting results from a GUI.
Read the post →Use ClickHouse from a desktop SQL client: HTTP ports, system tables for size and slow queries, EXPLAIN indexes = 1, and safety without transactions.
Read the post →How SQLly stops an UPDATE or DELETE with no WHERE clause: editor warnings, a confirmation gate, read-only connections, rollback wraps and production locks.
Read the post →How SQLly streams a 50-million-row result: batched reads, a back-pressured channel, spill-to-disk past a threshold, and a grid that pages from the file.
Read the post →Schema-aware SQL completion in SQLly: JOIN ON clauses from real foreign keys, stable aliases, real column values, and an F2 loop that turns misses into tests.
Read the post →