Re: mysql BUG, again ;)
On Tue, 29 Jul 2003, Dyego Souza do Carmo wrote: > >I would like to know if you could fix the bug I reported to you >some days ago. > >The error is: "ERROR 1030: Got error 139 from table handler" after >running an update command using several blobs. > >Now I am using mySql 4.0.15 and Linux. If you try to do the same >with mySql 4.0.14, the record that is updated is simple deleted. Please post your bugs to http://bugs.mysql.com It is a tracking system for bugs. > My System is a Debian Linux box , with kernel 2.4.20 with 768 of RAM > using InnoDB tables ;) > > InnoDB,MyISAM,SQL > > > > > - > ++ Dyego Souza do Carmo ++ Dep. Desenvolvimento > - > E S C R I B A I N F O R M A T I C A > - > The only stupid question is the unasked one (somewhere in Linux's HowTo) > Linux registred user : #230601 > --ICQ : 1647350 > $ look into "my eyes" Phone : +55 041 296-2311 > look: cannot open my eyes Fax : +55 041 296-6640 > - >Reply: [EMAIL PROTECTED] > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] > -- Boyd Gerber, Software Engineer & Support Specialist MySQL AB, www.mysql.com Are you MySQL certified? www.mysql.com/certification -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql BUG, again ;)
Dyego, but now it works right. [EMAIL PROTECTED]:~/mysql-standard-4.0.8-gamma-pc-linux-i686/bin> perror 139 Error code 139: Unknown error 139 139 = Too big row (>= 16 M) The error message text above is wrong, though :). This has nothing to do with 16 MB. You should not put THAT many BLOBs in the same row. Split the table vertically into several. InnoDB-4.0.14 stores the first 512 bytes of each BLOB into the clustered index record. If you have > 14 BLOBs, then the clustered index record will be > 8000 bytes long, and you get the error above. Regards, Heikki .... Subject: mysql BUG, again ;) From: Dyego Souza do Carmo Date: Tue, 29 Jul 2003 09:40:17 -0300 Hi, I would like to know if you could fix the bug I reported to you some days ago. The error is: "ERROR 1030: Got error 139 from table handler" after running an update command using several blobs. Now I am using mySql 4.0.15 and Linux. If you try to do the same with mySql 4.0.14, the record that is updated is simple deleted. My System is a Debian Linux box , with kernel 2.4.20 with 768 of RAM using InnoDB tables ;) InnoDB,MyISAM,SQL - ++ Dyego Souza do Carmo ++ Dep. Desenvolvimento - E S C R I B A I N F O R M A T I C A -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql BUG, again ;)
Hi, I would like to know if you could fix the bug I reported to you some days ago. The error is: "ERROR 1030: Got error 139 from table handler" after running an update command using several blobs. Now I am using mySql 4.0.15 and Linux. If you try to do the same with mySql 4.0.14, the record that is updated is simple deleted. My System is a Debian Linux box , with kernel 2.4.20 with 768 of RAM using InnoDB tables ;) InnoDB,MyISAM,SQL - ++ Dyego Souza do Carmo ++ Dep. Desenvolvimento - E S C R I B A I N F O R M A T I C A - The only stupid question is the unasked one (somewhere in Linux's HowTo) Linux registred user : #230601 --ICQ : 1647350 $ look into "my eyes" Phone : +55 041 296-2311 look: cannot open my eyes Fax : +55 041 296-6640 - Reply: [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
