Marco Turrini wrote:
And I believe you are missing the point, the starting one, to be precise. I replied to Jeremy Fowler
I could have sworn, that your original point, was the following....
Marco Turrini wrote:
Using char(1) for a boolean is stupid enough, ... 3) Using [var]char introduce wide possibilities for unnecessary errors and runtime exceptions.
I don't see anything that qualifies that statement with something about reports that export those values directly.
Marco Turrini wrote:
Although I appreciated your thouroghly lesson above, I can't understand what this has to do with defending the use of a char data type for boolean value:
In point of fact I don't really see why it matters whether one chooses one or the other. Either can lead to problems when used incorrectly. When used correctly neither will.
Marco Turrini wrote:
But if I have such a layer, why shouldn't I use a bit data type in the database to express boolean values?
And why should insist on using a bit type and assert that the alternative is contemptible (which 'stupid' suggests.)
Marco Turrini wrote:
I find that using a char(1) could be preferable just in two circumstances:
And as far as I can see the only arguments for that point of view are one of the following: 1. A very, very limited market segment which should be driven by marketing not technological reasons. 2. A very, very flawed architecture which requires that data types flow throughout the system.