I never noticed that setting. I'm guessing it's app-wide simplifies things otherwise making it per column would mean having two different types of yes/no choices in the column builder.
My memory from my programming days is that in databases the empty or Null choice was considered a design misfeature because it tended to introduce hard to find programming errors, or maybe it was that queries were more difficult to get right. Although in databases the null value could be used in any type, not just true/false yes/no, but regardless was a bad "code smell".
|