easyGXBank · schema-design
Close the loophole on a column that's never actually null
customers.email is declared as a nullable TEXT column, but every process that writes to this table already requires an email — none of the existing rows have one missing. The nullability is just an oversight from when the table was first created.
Add a NOT NULL constraint to customers.email so the database enforces what's already true of the data.
Schema
▸customers
| id | INT |
| TEXT | |
| name | TEXT |
Example input
▸customers
Stuck? Ask the coach for a nudge that won't give the answer away, or reveal the reference solution and a short walkthrough of why it works.