MySQL Bugs: #39134: Obsolete info about types

Bug #39134	Obsolete info about types
Submitted:	29 Aug 2008 21:32	Modified:	30 Aug 2008 5:22
Reporter:	Federico Razzoli (OCA)	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
URL:
http://dev.mysql.com/doc/refman/5.0/en/other-vendor-data-types.html

The page says that MySQL users can use TINYINT datatype in place of other dbms's BOOL and BOOLEAN. But MySQL 5.0 supports those types!
Also, why should old versions users use a 4 bytes datatype instead of ENUM('0', '1') or CHAR(1)?

How to repeat:
.

Sorry, but TINYINT uses 1 byte to store values. Also, BOOLEAN is just a synonym of TINYINT(1) in MySQL. So, whenever you use it column of TINYINT(1) type is created:

mysql> create table tboo(c1 boolean);
Query OK, 0 rows affected (0.14 sec)

mysql> desc tboo;
+-------+------------+------+-----+---------+-------+
| Field | Type       | Null | Key | Default | Extra |
+-------+------------+------+-----+---------+-------+
| c1    | tinyint(1) | YES  |     | NULL    |       |
+-------+------------+------+-----+---------+-------+
1 row in set (0.03 sec)

See also http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html.

I do not see any problem in documentation here.