chinook-database VS pagila

In literally 30 seconds, you can open the blog post, upload a SQLite file, and then query it in the Splitgraph web console (or via HTTP, or via any Postgres client). Authentication is not required.

Here's the 30 second video [0] and end result [1]. If you don't have a SQLite file handy and want to try it yourself, here's a link to the Chinook Database [2].

[0] Video (30 seconds): https://twitter.com/splitgraph/status/1646612048837591040

[1] Repository: https://www.splitgraph.com/miles/chinook-tables/latest/-/tab...

[2] chinook.sqlite: https://github.com/lerocha/chinook-database/blob/e7e6d5f008e...

I’ll be using a Postgres datasource (the famous Chinook database) for my example, using WunderGraph to make it accessible through JSON-RPC to my Next.js frontend.

If you look at a typical SQL query in analytics, it looks something like this (taken from Chinook sample database):

schemacrawler/chinook-database builds on the earlier project. The project has an automatic build using GitHub Actions, which pulls scripts from lerocha/chinook-database, cleans them up, and converts them all to UTF-8 with consistent line-endings. Then are are repacked and redistributed in various ways - as a Java jar file for use in Java programs or in tests with database in Testcontainers. The SQLite database can be directly download from the project site. But probably the best way to use the package it is use the Docker image from schemacrawler/chinook-database to create the Chinook database on a database of your choice, whether the database server is running on a separate host or within a Docker container itself.

https://github.com/lerocha/chinook-database#:~:text=Chinook%20is%20a%20sample%20database,single%20and%20multiple%20database%20servers.

The tutor told us that he wrote the whole file for us, but now thanks to both your leads I have found out that the file PAGILA is a GIT project at https://github.com/devrimgunduz/pagila , the "translation" of Sakila training database for MySQL.

One day, I was puzzled about how to generate some random data for development and testing without leaving my warm SQL console (in my case, psql). That’s when this set of SQL-scripts was born to generate a large amount of data for Pagila, a popular PostgreSQL sample database. You can find these scripts here: https://github.com/synthesized-io/pagila-data-generation (in "sql" folder) – and adapt them to your database schemas. I would be extremely grateful for any advice and ideas.

Create HTTP and/or gRPC server for pagila database (DVD rental database). Each server should expose metrics for scraping as well as emit traces (either to Zipkin or Jaeger, or if you feel adventurous you can support both). Start with either HTTP or gRPC and first implement just Customer service that would return customer by ID and allow inserting new one, that should be good start. When done with server(s) create GUI applications, one native, one for web (Rust + WebAssembly). Everything should be pushed to GitHub, have GitHub Actions configured for tests and build.

You can get interesting sample db here: https://github.com/devrimgunduz/pagila - it uses quite a lot of different features of pg, including fkeys.

Would running a sample database in a container also be too much? You could have some example images with a schema like Pagila loaded into them.