Some early morning thoughts on lesson design and implementation (thread). I just converted a hand-drawn (i.e., illegible to anyone but me) concept map into something readable and posted it in the SQL tutorial (https://gvwilson.github.io/sql-tutorial/img/concept_map_datamod.svg). Problem is, the lesson as implemented doesn't line up with the design: blobs and some of the row constraints mentioned in the diagram haven't been introduced at this point. 1/
@gvwilson Many thanks for this thread!. I teach a full #Databases course and struggle with this too. Mostly following your strategy B. Cannot think of a PR that would improve the tutorial, unfortunately...
In order to sort items in a table you use a "sort key", but then when you want to delete one of the items in the table you then have to provide the primary key and the sort key.
I get why; it's partitioning based on keys, and the sort key is part of the compound key, so it needs it to fully address the row you're deleting.
Open source CockroachDB tempts legacy databases to crawl into the cloud age
CockroachDB is a distributed SQL database built on a transactional and strongly-consistent key-value store. It scales horizontally; survives disk, machine, rack, and even datacenter failures with minimal latency disruption and no manual intervention; supports ...continues
Another fun fact about Misskey: some of the defederation logic works by inserting the entire list of blocked instances directly into each individual query. This, of course, kills the Postgres.