MySQL's Bit

[quote=337938:@Norman Palardy]More often than not under the hood the db engine saves VERY little space using a bit field vs a one byte int (tinyint)
And mysql is this way as well
See https://dev.mysql.com/doc/refman/5.6/en/storage-requirements.html

a single bit in a column still takes 1 byte

ie/ its a “false savings” - store 0 and 1 in a tiny int and that should be just as easy to turn into a boolean :)[/quote]
True, for a single bit column. In SQL Server if you have multiple bit columns it will optimize the storage (see https://docs.microsoft.com/en-us/sql/t-sql/data-types/bit-transact-sql).
But SQL Server only has a single “bit” bit data type, whereas MySQL, PostgreSQL (and probably others) have a “bit string” data type, where the length is the number of bits you want to store. So optimizing storage for those would be more complicated.