I am curious if there are any major differences with performance and/or conventionality regarding which binary data types one chooses. Let's say I have a table of metallic objects and I am considering to create a binary field to record whether or not the object is reflective.
reflective BIT NOT NULL DEFAULT 0 -- 0 for nonreflective 1 for reflective reflective CHAR(1) NOT NULL DEFAULT 'F' -- False for nonreflective, True for reflective reflective ENUM('N','R') NOT NULL DEFAULT 'N' -- N for nonreflective R for reflective. reflective ENUM('nonreflective','reflective') DEFAULT 'nonreflective' -- I think this takes up the same amount of storage resources but is clearer
ENUM aside, they all seem more or less equal in terms of readability, and while I'm not exactly sure which would make for most efficient scaling and querying, I'd venture they would all be comparable. Am I right in this assumption; is the binary data structure largely arbitrary, or are there trade-offs I should be aware of?
Also I'd be interested to know if among these examples (or structures I did not include) there is a clear convention, and why.