Trouver un outil

↑↓ parcourir Enter ouvrir

Recherchez par tâche si vous ne connaissez pas le nom exact.

SQLite Workspace

Traitement local

SQLite Workspace permet de inspecter des données dans le navigateur et présente clairement le résultat et ses limites. Cette page contient un exemple réel d’entrée et de sortie, les limites d’implémentation et les sources primaires de cet outil.

Vérifié · Mis à jour · Gratuit · Sans compte

Open/create/sample replaces the current in-memory database. Export changes before replacing it or leaving this page. Original files stay unchanged. Stop closes the database and discards unexported changes. No automatic saving.

No database open. Choose a local file up to 25 MiB, or create a database.

Tables, views and schema (up to 100)
Result JSON
One statement per run, up to 64 KiB; preview: 500 rows, 64 columns, 2 MiB.
SQL and database bytes stay in this tab. SQLite WASM loads from this site.

Que fait SQLite Workspace ?

SQLite Workspace permet de inspecter des données dans le navigateur et présente clairement le résultat et ses limites. Fonctions vérifiées : Local database import and creation, Table and view schema browser, SQL queries and in-memory edits, Database and query JSON export.

When should you use this tool?

Use this workspace to inspect and make small changes to local SQLite files without a server. Use SQL Formatter for formatting alone and a desktop SQLite client for large files, encrypted databases, transactions, exact 64-bit integer workflows or durable storage.

Comment l’utiliser ?

  1. Open a database up to 25 MiB, or choose New database / Sample database. Replacing it discards unexported changes.
  2. Enter one statement up to 64 KiB and select Run. Inspect the table or JSON preview; use LIMIT for large queries.
  3. Export the database to save edits. Download JSON for the current preview; closing the tab or stopping the Worker discards in-memory changes.

Exemple réel d’entrée et de sortie

Query adult users in the sample

Entrée

SELECT name, age FROM people WHERE age >= 18 ORDER BY age;

Sortie

name  | age
Ada   | 32
Grace | 40

The sample database contains Ada (32), Linus (17) and Grace (40). This query selects two adult rows. INSERT, UPDATE and DELETE change only the in-memory database until you export it.

Erreurs fréquentes et corrections

SymptômeCause probableCorrection
The database cannot be opened.It is encrypted, not a SQLite file, corrupt or larger than 25 MiB.Choose an unencrypted SQLite database. A server connection URL or a SQL dump is not a database file; no remote connection is attempted.
A query fails or results are truncated.SQL syntax, unsupported control statements or preview limits prevent a full result.Run one ordinary statement, reduce selected columns and add LIMIT. The preview is capped at 500 rows, 64 columns and about 2 MiB; exported databases retain the full data.

Supported behavior and limitations

Limite propre à cet outil : Data lives only in this tab, without automatic saving. Open/create/sample replaces the current database. Stop or the 15-second timeout closes it and discards unexported changes. Input files: 25 MiB; database growth is limited to about 64 MiB. One SQL statement per run, no file attachments, transaction-control commands, VACUUM or general PRAGMA (table/index/foreign-key introspection is supported). BLOB previews show 32 bytes, text cells 4096 characters; long cells are marked. Integers use JavaScript number precision. Large operations may still exceed browser memory; work on copies.

Normes et références d’implémentation

SQLite Workspace — FAQ

Is my input uploaded?

No. Processing happens in a browser Worker. Engine files load from this website; tool input, output, and filenames are not sent to a processing API.

Do I need an account or API key?

No account, API key, or backend processing service is needed.

How do I save a result?

Review the result, then use the Copy or Download control available for that output. Modifying input clears stale results.

What are the limits?

Data lives only in this tab, without automatic saving. Open/create/sample replaces the current database. Stop or the 15-second timeout closes it and discards unexported changes. Input files: 25 MiB; database growth is limited to about 64 MiB. One SQL statement per run, no file attachments, transaction-control commands, VACUUM or general PRAGMA (table/index/foreign-key introspection is supported). BLOB previews show 32 bytes, text cells 4096 characters; long cells are marked. Integers use JavaScript number precision. Large operations may still exceed browser memory; work on copies.

Quelles modifications ?

Mise à jour substantielle : SQLite Workspace: Added local processing, explicit size limits, cancellation, worked examples, error explanations, and downloadable results.

Qui maintient cet outil ?

KL
KitLumi EngineeringKitLumi Engineering maintient le comportement, les tests, les exemples et les informations de confidentialité.