True/False vs 0/1 in MySQL

Question

Which is faster in a MySQL database? Booleans, or using zero and one to represent boolean values? My frontend just has a yes/no radio button.

I have a related observation when using MySQL with the MySqlDataReader for C#.NET. When I create a column of type BOOLEAN, it ends up as TINYINT(1) and the values look like 0s and 1s in PHPMyAdmin. However when SELECTed programmatically using MySqlDataReader, the values returned are the strings "True" and "False", (exact capitalization). This happens to work nicely with C#.NET's bool.Parse(), which only accepts the strings "True" and "False". I guess MySqlDataReader was deliberately built this way for convenience. — Doochz
– Doochz, Commented Aug 27, 2013 at 11:39
Please note that MySql now has a BIT type. See this answer for more information. — Xynariz
– Xynariz, Commented Feb 24, 2014 at 18:16
You're using a radio button for Yes/No?!? What's wrong with a checkbox/tickbox? — Caltor
– Caltor, Commented Dec 17, 2014 at 11:47

Marcus Adams · Accepted Answer · 2012-06-01 14:56:19Z

Some "front ends", with the "Use Booleans" option enabled, will treat all TINYINT(1) columns as Boolean, and vice versa.

This allows you to, in the application, use TRUE and FALSE rather than 1 and 0.

This doesn't affect the database at all, since it's implemented in the application.

There is not really a BOOLEAN type in MySQL. BOOLEAN is just a synonym for TINYINT(1), and TRUE and FALSE are synonyms for 1 and 0.

If the conversion is done in the compiler, there will be no difference in performance in the application. Otherwise, the difference still won't be noticeable.

You should use whichever method allows you to code more efficiently, though not using the feature may reduce dependency on that particular "front end" vendor.

This isn't entirely correct. TRUE and FALSE are not necessarily equivalent with 1 and 0. For one, they behave very differently when used in combination with the IS operator. For example, WHERE NOT(something IS 1) would be a syntax error, but WHERE NOT(something IS TRUE) works.
@MattZukowski, TRUE and FALSE are synonyms for 1 and 0, but the reverse is not true. 0 is not a synonym for FALSE, and 1 is not a synonym for TRUE, and this is why TRUE IS 1 will give a syntax error, but 1 IS TRUE will not.
@MarcusAdams "synonym" is the wrong word then; "alias" is better

informatik01 · Accepted Answer · 2019-08-08 12:26:37Z

In MySQL TRUE and FALSE are synonyms for TINYINT(1).

So therefore its basically the same thing, but MySQL is converting to 0/1 - so just use a TINYINT if that's easier for you

P.S.
The performance is likely to be so minuscule (if at all), that if you need to ask on StackOverflow, then it won't affect your database :)

no. BOOL and BOOLEAN are synonyms for TINYINT(1). TRUE & FALSE are literals. Different category.

Community · Accepted Answer · 2020-06-20 09:12:55Z

Bit is also an option if tinyint isn't to your liking. A few links:

Not surprisingly, more info about numeric types is available in the manual.

One more link: http://blog.mclaughlinsoftware.com/2010/02/26/mysql-boolean-data-type/

And a quote from the comment section of the article above:

TINYINT(1) isn’t a synonym for bit(1).

TINYINT(1) can store -9 to 9.

TINYINT(1) UNSIGNED: 0-9

BIT(1): 0, 1. (Bit, literally).

Edit: This edit (and answer) is only remotely related to the original question...

Additional quotes by Justin Rovang and the author maclochlainn (comment section of the linked article).

Excuse me, seems I’ve fallen victim to substr-ism: TINYINT(1): -128-+127 TINYINT(1) UNSIGNED: 0-255 (Justin Rovang 25 Aug 11 at 4:32 pm)

True enough, but the post was about what PHPMyAdmin listed as a Boolean, and there it only uses 0 or 1 from the entire wide range of 256 possibilities. (maclochlainn 25 Aug 11 at 11:35 pm)

You are incorrect; TINYINT(1) can store more distinct values than that; the (1) limit only affects how these values are displayed.
@cnst See the edit. The whole answer is quite unrelated to the original question but at least it provides some information about the subject. BTW: simple select * from table_x displays the whole value of tinyint(1) column even if it is a two or three digit number.

eduard · Accepted Answer · 2012-06-02 16:15:58Z

If you are into performance, then it is worth using ENUM type. It will probably be faster on big tables, due to the better index performance.

The way of using it (source: http://dev.mysql.com/doc/refman/5.5/en/enum.html):

CREATE TABLE shirts ( name VARCHAR(40), size ENUM('x-small', 'small', 'medium', 'large', 'x-large') );

But, I always say that explaining the query like this:

EXPLAIN SELECT * FROM shirts WHERE size='medium';

will tell you lots of information about your query and help on building a better table structure. For this end, it is usefull to let phpmyadmin Propose a table table structure - but this is more a long time optimisation possibility, when the table is already filled with lots of data.

Collectives™ on Stack Overflow

True/False vs 0/1 in MySQL

4 Answers 4

3 Comments

1 Comment

2 Comments

Comments

Linked

Hot Network Questions