How do I avoid modeling errors? | Designing for Easy SQL Selects Pt 2
Sign up for DUTC Weekly: https://mailchi.mp/dutc/ytweekly
LinkedIn: / do-n-t-use-this-code
Website: https://www.dontusethiscode.com/index...
Upcoming events: learning.dutc.io
Looking for training? Contact [email protected]
This is part of the Confident Queries & Stronger SQL - Hard Selects for Complex Analyses series.
Do you…
need to figure out how to design a data pipeline that writes-to and reads-from an SQL database?
want to make your life easier when you query your database tables?
want your queries on historical data to always give repeatable results, even if your database data is constantly (ahistorically) updated?
worry that (preventable) errors in data input lead to critical analytical mistakes?
In this series, we’ll discuss how to approach the design of our tables and data pipelines to make them amenable to easy analysis with SQL. We’ll discuss the necessity of bitemporal design when working with (external) temporal data. We’ll cover common SQL/DDL-level mechanisms such as constraints, primary keys, and foreign keys, and when they are appropriate tools for our use. We’ll discuss anomalies that might appear in our data and how to apply simple forms of table normalization to avoid these issues. Finally, we’ll discuss some theory of database design and querying, such as transactions, transactional properties (ACID), and isolation levels.
Disclaimer: This series will include PostgreSQL specific features & functionality that may not be present in other database products like MariaDB, MySQL, or SQLite.