SQLite Workspace은(는) 무엇을 하나요?
SQLite Workspace은(는) 브라우저에서 데이터 검사을(를) 수행하며 결과와 제한을 명확히 설명합니다. 검증된 기능: 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.
사용 방법
- Open a database up to 25 MiB, or choose New database / Sample database. Replacing it discards unexported changes.
- Enter one statement up to 64 KiB and select Run. Inspect the table or JSON preview; use LIMIT for large queries.
- Export the database to save edits. Download JSON for the current preview; closing the tab or stopping the Worker discards in-memory changes.
실제 입출력 예시
Query adult users in the sample
입력
SELECT name, age FROM people WHERE age >= 18 ORDER BY age;출력
name | age
Ada | 32
Grace | 40The 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.
일반적인 오류와 해결 방법
| 현상 | 가능한 원인 | 해결 방법 |
|---|---|---|
| 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
이 도구의 구체적인 제한: 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.
표준 및 구현 참고 자료
- sql.js official repository (opens in a new tab)MIT JavaScript wrapper with public-domain SQLite, supporting browser import and export. The WASM engine is served locally.
- SQLite SELECT documentation (opens in a new tab)Authoritative query syntax; the tool applies its own single-statement and preview limits.
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.
변경 사항
실질적인 업데이트: SQLite Workspace: Added local processing, explicit size limits, cancellation, worked examples, error explanations, and downloadable results.