yes that was the post that caught my attention. however if your interpretation is right, then it will be a pain (from implementation point of view of DB) if
... remember also that a char(x) NULL column is actually a varchar(x) NULL column. A char column is incapable of holding a null, so behind the scenes SQL will
IMHO, Internally using varchar to implement char will defeat the entire purpose of char. Also it seems to a really convoluted design for implementing char.
yes that's the general rule. and even i was under the impression that char would be faster so should be used when it comes to fixed size data. what i was