Both databases run inside the browser tab, and the data stays put as students work. An INSERT in one exercise is still there in the next.
No database server, connection strings, or accounts to set up. Students open the page and run a query on a Chromebook, an iPad, or offline.
SQLite runs first, and a second run reads back the rows the first one inserted. A new file joins in. When the code changes to PostgreSQL, the database switches too.
This demo is scripted. No database runs on this page.
Students run SQLite and PostgreSQL with nothing to set up before their first query.
SQLite for a first course. PostgreSQL when you need window functions, SERIAL, or generate_series.
Insert or update rows, then query them right back. Students see cause and effect.
Attach a database to an exercise. Students open it with the data already loaded.
Exercises on a textbook page share one database. Build a schema at the top and query it at the bottom.
Alps picks SQLite or PostgreSQL based on the code. One click switches it.
Split work into several .sql files. Run one, or run them all in order on the same database.
| Feature | In the browser | On the server |
|---|---|---|
| Speed | Instant, since nothing leaves the tab | A round trip per run |
| Same engine, same answers | ||
| Database stays live across exercises | Fresh database each run | |
| Works offline | ||
| Start from a ready-made database | ||
| Result grids |
Queries run in the browser by default, and that covers a whole course. Server runs are there when a course needs them. Both use the same engine, so a query that works in one works in the other.
We can bring your own SQL material onto Alps as an interactive course. We also work with publishers and support licensed editions.
SQLite and PostgreSQL run in the browser, with nothing to install and no server to connect to.