The build just failed. The logs point to a missing field. You need a new column, and you need it now.
Creating a new column is one of the most common changes in any database schema. It should be fast, safe, and reversible. Done wrong, it can lock tables, block writes, and slow down production. Done right, it can roll out instantly, without downtime.
Start with a clear plan. Identify the table. Define the column name, type, and constraints. Use consistent naming, avoid reserved words, and ensure the default value is explicit. In SQL, adding a new column is usually a single ALTER TABLE statement. In most cases:
ALTER TABLE users ADD COLUMN last_login TIMESTAMP DEFAULT NOW();
On large datasets, this can be risky in production. Many relational databases will rewrite or lock the table. For PostgreSQL, adding a column with a default value not computed per row can rewrite the entire table. Mitigate by first adding the column as nullable, then updating rows in small batches. Finally, set the default.