The table was ready, but the data was wrong. A single missing column broke the query, the API, and the release window.
Creating a new column is trivial in theory. In production, it is a precise act with lasting consequences. Schema changes propagate across code, pipelines, and caches. A careless alteration can lock a table or block writes under load.
In SQL, adding a new column means using ALTER TABLE. This works for most relational databases, but the cost depends on storage engine and index design. Some databases can add a column instantly if it is nullable with a default value. Others rewrite the full table. In PostgreSQL, ALTER TABLE ... ADD COLUMN is fast for NULLable fields. MySQL’s InnoDB can be more expensive unless online DDL is enabled.
For NoSQL systems, adding a field is more about updating the application and the ETL jobs than the store itself. Documents in MongoDB or DynamoDB can simply start including the new key, but queries, indexes, and consuming services still need an update.