Closed deepankar-j closed 2 years ago
@danschultzer : Please let me know if you have any questions or concerns about this change.
Thanks! I've released v1.0.27 that resolves this issue. The null: false
was still required to make sure that the generated migration has it.
Ah, I see. Thanks @danschultzer!
Ecto v3.8.0 throws an error when it encounters unsupported options. It turns out that :null isn't a valid field option.