Is this a real SQL database?+
Yes. It uses SQLite via sql.js compiled to WebAssembly, giving you the full power of SQLite including CREATE, INSERT, UPDATE, DELETE, and complex SELECT statements.
Does my data persist between sessions?+
No. The database lives in browser memory and is cleared when you close or refresh the tab. For persistent data, you'll need a real database server.
Which SQL features are supported?+
All SQLite-supported SQL: CREATE TABLE, INSERT, SELECT with JOINs, GROUP BY, HAVING, ORDER BY, subqueries, CTEs (WITH), and most standard functions.
Can I import data from a CSV or existing database?+
Not directly in this tool. You can paste INSERT statements to load data manually. To import CSV, convert it to INSERT statements first using a CSV-to-SQL tool.
Which SQL dialect does the online playground use?+
The playground uses SQLite via sql.js (WebAssembly). SQLite supports most standard SQL including CTEs, window functions, and full-text search. It differs from MySQL and PostgreSQL in some areas: no FULL OUTER JOIN, no stored procedures, and limited ALTER TABLE support.
Can I save my SQL queries for later?+
The tool does not have persistent server-side storage. Copy your SQL to a text file or use your browser's local storage via the 'Save Query' button if available. For collaborative query management, use a dedicated tool like DBeaver or DataGrip.
Can I run JOIN queries in the playground?+
Yes. Create multiple tables with CREATE TABLE and INSERT statements, then write SELECT queries with INNER JOIN, LEFT JOIN, or CROSS JOIN. The playground handles JOINs, subqueries, GROUP BY, and window functions fully.
How do I import CSV data into the SQL playground?+
SQLite's sql.js doesn't support CSV import directly. Paste your data as INSERT statements, or use the CSV-to-SQL converter tool to generate INSERT statements from your CSV file, then paste those into the playground.
Are there performance limits for queries in the playground?+
The playground runs entirely in your browser with no server-side query timeout. Very large datasets (millions of rows) will consume browser memory and slow performance. For realistic benchmarking, test against an actual database server.