Sentinel values and fake NULLs

Concepts covered: sqlNullif

Sentinel Values Many software systems are forced to produce values even when the data isn't known. This happens for several reasons: When a system must produce a value but doesn't know the real answer, developers choose "placeholder" values. These sentinel values become embedded in the data and persist for years. Common Sentinel Values These placeholders may seem harmless, but they complicate every query that touches the column. Practical Implications Consider why these patterns emerge in actual systems: Empty String vs NULL In practice, most systems don't track this distinction. Form submissions often send '' for unanswered questions, and databases store it as-is. The meaning of "unknown" gets lost. Detection and Handling When analyzing data, you must understand what placeholder values ex

About This Interactive Section

This section is part of the NULL Values: Intermediate lesson on DataDriven, a free data engineering interview prep platform. Each section includes explanations, worked examples, and hands-on code challenges that execute in real time. SQL queries run against a live PostgreSQL database. Python runs in a sandboxed Docker container. Data modeling problems validate against interactive schema canvases. All content is framed around what data engineering interviewers actually test at companies like Meta, Google, Amazon, Netflix, Stripe, and Databricks.

How DataDriven Lessons Work

DataDriven combines four interview rounds (SQL, Python, Data Modeling, Pipeline Architecture) with adaptive difficulty and spaced repetition. Easy problems get harder as you improve. Weak concepts resurface until you master them. Your readiness score tracks progress across every topic interviewers test. Every lesson section ends with problems you solve by writing and running real code, not by picking multiple-choice answers.