chDB SQL Shell

At a glance

chDB SQL Shell runs the ClickHouse SQL engine in your browser through WebAssembly, without setting up a database server. It is worth trying for a small SQL experiment or a first look at ClickHouse’s query syntax. Processing happens on your device, but the shell is an in-memory session rather than a durable shared database.

Good fit

Developers who want to test an expression, learn analytical SQL or explore a supported file with a terminal-style interface. The generated-row example returned numbers zero through nine with their squares; a filtered aggregation returned the expected sum of ten. That is a useful first step before deciding whether to embed chDB in an application or operate a database service.

Consider something else when

You need persistent tables, shared access, scheduled jobs or evidence that a large dataset will fit comfortably in memory. The source opens an in-memory connection; New clears history and registered files and reconnects. Browser hardware and WebAssembly constraints still apply even though there is no server to configure.

Start here

Wait for the engine to initialize, choose Examples, then Generated rows, and press Enter to execute the filled-in SQL. Expect ten rows with a number and its square. Try changing numbers(10) to a smaller count. Enter runs the query; Shift+Enter inserts a new line. Import registers selected local files for queries using the file() function; remote URL/S3 examples are a separate network-using workflow.

Cost and requirements

The public shell worked without an account, payment or native installation. The shell package declares Apache-2.0 licensing and consumes the separate chdb-wasm engine package. It needs a compatible browser and an initial engine download; the hosted page supplies the isolation headers used by its threaded build. Queries use your device’s memory and compute. Local SQL execution does not prevent remote-file queries from contacting an external host.

Limits to know

The trial covered small generated queries, a missing-table error and recovery with SELECT 42 AS answer; it did not import files, contact remote data sources, test cancellation or measure large-query performance. Source code registers picked files with the engine rather than a query backend. No traffic audit, mobile compatibility check or file-size limit was established, so sensitive-file suitability should not be inferred from this trial.

Still unclear

• What practical file size and memory ceiling will this browser and device sustain? The small generated-row trial does not establish those limits.