Post #1860154
2026-05-01 17:10 UTC
RE: https://mas.to/@davidism/116483352787950950
Was surprised how close this stayed. At a few points it was an even 50/50 split. No one picked the chaos option, which is a good sign. People made good arguments for both options. A little confusion over "default" whether that was at the SQL, form, or code level. I ended up picking "not null, default empty" for my current project because I don't need to distinguish "no response" from "empty response", so that simplifies typing. #python #flask #django
Replies (1)
-
@coderanger@cloudisland.nz 2026-05-01 18:29
@davidism@mas.to a thing i didn’t see in the comments, Django puts its finger on the scale because db_default is such a new feature, prior to that you had to with nullable when adding a new column or it would break during rollout.