# Analysis Of Implicit Data Type Conversions (Continued...)

+ Table definition:
```
CREATE TABLE t1 (
 id int(11) NOT NULL AUTO_INCREMENT,
 ~!@k int(11)@!~ NOT NULL DEFAULT '0',
 c char(120) NOT NULL DEFAULT '',
 pad char(60) NOT NULL DEFAULT '',
 PRIMARY KEY (id) ,
 ~!@KEY k_1 (k)@!~
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin AUTO_INCREMENT=1389756;
```

------------------------------------------------------------

Let's look at another case. There is a new table t1 with the following table schema:

```
CREATE TABLE t1 (
 id int(11) NOT NULL AUTO_INCREMENT,
 k int(11) NOT NULL DEFAULT '0',
 c char(120) NOT NULL DEFAULT '',
 pad char(60) NOT NULL DEFAULT '',
 PRIMARY KEY (id) ,
 KEY k_1 (k)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin AUTO_INCREMENT=1389756;
```

Here, the k column is of type int. Let's look at the execution plan of the following query: