MySQL Lists are EOL. Please join:

List:General Discussion« Previous MessageNext Message »
From:Heikki Tuuri Date:July 29 2003 3:02pm
Subject:Re: mysql BUG, again ;)
View as plain text  

but now it works right.

heikki@hundin:~/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



Subject: mysql BUG, again ;)
From: Dyego Souza do Carmo
Date: Tue, 29 Jul 2003 09:40:17 -0300


   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 ;)


  ++  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 BUG, again ;)Dyego Souza do Carmo29 Jul
  • Re: mysql BUG, again ;)Boyd Lynn Gerber29 Jul
Re: mysql BUG, again ;)Heikki Tuuri29 Jul