Comments on: MySQL Data Type Q&A http://themattreid.com/wordpress/2009/02/26/mysql-data-type-qa/ MySQL DBA | Linux'er Thu, 26 Apr 2012 16:12:57 +0000 hourly 1 By: Salman http://themattreid.com/wordpress/2009/02/26/mysql-data-type-qa/comment-page-1/#comment-565 Salman Fri, 09 Mar 2012 20:01:40 +0000 http://themattreid.com/wordpress/?p=105#comment-565 mysql data type tinyint(2) here what means by 2 the range of tinyint is -128 to 127 or 0 to 255 but the fact is in tinyint(2) when we create table here 2 means what .. when i write tinyint(2) it also accept number with in the tinyint range and if i write like tinyint(1) or tinyint(4) it that also accept the range then here tinyint(2) what the 2 means.. mysql data type tinyint(2) here what means by 2 the range of tinyint is -128 to 127 or 0 to 255 but the fact is in tinyint(2) when we create table here 2 means what .. when i write tinyint(2) it also accept number with in the tinyint range and if i write like tinyint(1) or tinyint(4) it that also accept the range then here tinyint(2) what the 2 means..

]]> By: Stefan http://themattreid.com/wordpress/2009/02/26/mysql-data-type-qa/comment-page-1/#comment-67 Stefan Thu, 26 Feb 2009 22:59:04 +0000 http://themattreid.com/wordpress/?p=105#comment-67 Don't you mean the VARCHAR(1) column should be replaced with a CHAR(1) instead of TINYTEXT ? @stefan: agreed, I would personally use CHAR but I'm trying to explain why in this case proc analyse() would suggest TINYTEXT instead of VARCHAR Don’t you mean the VARCHAR(1) column should be replaced with a CHAR(1) instead of TINYTEXT ?

@stefan: agreed, I would personally use CHAR but I’m trying to explain why in this case proc analyse() would suggest TINYTEXT instead of VARCHAR

]]>