Field of the BIT type

to set the rightmost bit 1: update the bitset set data=data | 1
to set the rightmost bit to 0: update the bitset set data=data &~ 1
other bits as well (2, 4, 8, 16 ...)

habrahabr.ru/blogs/webdev/41458/
There are 2 links at the top, well, on the topic of the author, plus in the comments.
\r
To this dev.mysql.com/doc/refman/5.0/en/bit-functions.html
Plus don't forget about the feature BIT in the mysql portability issues, etc.
\r
If You talk about "each bit separately, without removing previous", then bits is still physically extracted, before your new bit will be recorded. Therefore, it is only about sql-change record a bit. Hence the binary operation is suitable.
\r
PS: Incidentally, I note that a search on fucking dev.mysql.com again, not working. Well, it is, for lovers of shit and all, to know the place.

Use an integer field through the layer. NULL is understood as a FALSE unity 1 is TRUE.
\r
The result:
1. Crossbase. At any time you can move from SQLite to MySQL and MySQL to PostgreSQL and Oracle, as well as exotic, and even a nosql database. Everything that supports the layer. If does not support — just write a new driver for the layer.
2. Not noticeable any significant changes in productivity and resources. Honestly, not much!
3. Convenient to use, convenient for programming, it is very convenient for standardization.
4. At any time you can extend the number of States of the entity. Pro stock there are 4 billion options...