Recently, we talked about extracting data from complex relational databases. This is -- in a way -- another case study for my Unlearning SQL book. This is a description of what comes next after the "low-level" conversion. Warning: it's complicated.

BLUF: Take the time to get rid of SQL processing.

We're talking about extracting data from complex relational databases. This is -- in a way -- another case study for my Unlearning SQL book.

We're talking about extracting data from complex relational databases. This is -- in a way -- another case study for my Unlearning SQL book.

We're talking about extracting data from complex relational databases. This is -- in a way -- another case study for my Unlearning SQL book.

Let's talk about extracting data from complex relational databases. This is -- in a way -- another case study for my Unlearning SQL book.

Big Announcement: the 2024.8 version of Unlearning SQL, and the 2024.9 version of Pivot to Python are available from booksellers online. Both are revised and all the code tested with Python 3.12.

Book (pre) Announcement:

• KDP - See https://www.amazon.com/stores/Steven-Lott/author/B00HNRSLEK for my author's page.

  https://www.amazon.com/Unlearning-SQL-hammer-every-problem-ebook/dp/B0DDMFMXNW is the book.

• Google Play - See https://play.google.com/store/books/details?id=23WAEAAAQBAJ. Be sure to get the 2024.08 edition; there's a previous …

Consider, for a moment, the shelve and dbm packages for storing things in a “database.” Built-in. Lightweight. The database is essentially a mapping from identifiers to objects. It can be quite nice.

The shelve module directly puts Python objects in a file. It’s an ideal database structure for Python …

Fundamentally, we need to provide explicit version identification on a schema. This is technically easy, but organizationally nearly impossible.

Technically, we need to use some kind of version control software for our model and the resulting DDL. We need some meta-meta-data to track schema names and version numbers. If we …

I've been asked about the proper location of Stored Procedures more than once. I've come down very strongly in opposition to triggers and stored procedures.

First, PL/SQL is slow . Anecdotally, people claim that introducing PL/SQL made an app faster. I submit that they restructured the application significantly to …