Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

OK, but why does that require the database to have non-nullable string types?


No reason per se, but it’s inconvenient and I’ve seen tons of bugs from “NoneType has no method ‘uppercase()’” that this eliminates.


Sorry, I can't get behind changing the database design to accommodate under-specified data contracts and/or lazy software development.


I can't get behind letting theoretical database design concerns trump real world problems with unexpected nulls leading to 500s in production. :-)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: