Now, let’s review the results for all individuals whose run was not completed by checking the value of the “runCompleted” column. Hence, we can conclude that both clauses work in the same manner.ħ. Query: SELECT * FROM marathon_players WHERE healthChecked IS NOT FALSE Now, let us use IS NOT FALSE clause and see whether we retrieve the same results. Any non-zero value, whether positive or negative, will be considered true. From the results, it is evident that both the values 1 and 12 are considered true.

For this, I will first use the clause IS TRUE, and my query statement will be as follows –Ĭode: SELECT * FROM marathon_players WHERE healthChecked IS TRUE Ħ. Let us try to find out the records in our table marathon_players whose healthChecked columns value is true or is equivalent to true. Out of them, IS TRUE and IS NOT FALSE behave in the same fashion, and IS NOT TRUE and similarly IS FALSE function and result in the same results. To know whether a particular column contains the value that evaluates to true or false, MySQL provides us with four clauses: IS TRUE, IS FALSE, IS NOT TRUE, and IS NOT FALSE clauses. IS TRUE, IS FALSE, IS NOT TRUE, IS NOT FALSE Clauses. Even though we declared those columns as BOOLEAN and BOOL, the database internally treated them as TINYINT datatypes, expanding the column length to store the values.ĥ. In the second record, we stored the values -12 and 25 in the healthChecked and runCompleted columns, respectively, using the same format that we declared. The insertion stored them as 1 and 0, respectively. In the first record, Ramesh’s name was inserted and we specified the healthChecked and runCompleted columns as true and false, respectively. Now, let’s execute the following select query to observe the retrieved resultsĤ. Query: INSERT INTO marathon_players (player_id, Name, Age, healthChecked, runCompleted, completionTime) VALUES('1','Ramesh','25','true','false','02:50:56') INSERT INTO marathon_players (player_id, Name, Age, healthChecked, runCompleted, completionTime) VALUES('2','Suresh','27','-12','25','01:30:21') ģ. Let us now insert some values in the marathon_players table using the following insert queries: We can conclude that MySQL automatically converts and treats the data type of the “healthChecked” column as TINYINT(1) and the data type of the “runCompleted” column as BOOL, even though we specified them as BOOLEAN. Now, let us describe the created table by using the following query statement: DESC marathon_players Įxecuting the above query gives the following outputĢ. For the table creation, we will use the following CREATE TABLE query. We will declare the data type of the healthChecked column as BOOLEAN and runCompleted as BOOL and check the results of the created table. Let us create one table named marathon_players that will store the participants’ details in the marathon and have columns that will store boolean values in it, such as healthChecked and runCompleted. Note that true and false are treated the same irrespective of the case in which they are used. Hence, we can conclude that MySQL considers true as one and false as 0.

The output of the above query statement is as follows

Mysql boolean field