Hello,
I am building a database, it requires each row to be about 60,000 bytes (very close to mysql max row size, basically lots of varchar(500) statements [Its a bad strucutre, but necessary]). now, that is ok in myism as far as I know.
However, I am considering innodb due to its row locking behaviour (I get lots of updates to my table). I have only just come across some troubling information regarding innodb not liking large rows (something about 8000 bytes max or something) - http://forums.innodb.com/read.php?3,1196,1204
So, given that my table must have rows of approx 60,000 bytes each, is this a problem for innodb? Is it a big problem? deal breaker? what would you suggest?
Table structure: ID (int, autoinc, primary key), varchar(500), varchar(500)...repeat...varchar(500) until end of table reached
I am building a database, it requires each row to be about 60,000 bytes (very close to mysql max row size, basically lots of varchar(500) statements [Its a bad strucutre, but necessary]). now, that is ok in myism as far as I know.
However, I am considering innodb due to its row locking behaviour (I get lots of updates to my table). I have only just come across some troubling information regarding innodb not liking large rows (something about 8000 bytes max or something) - http://forums.innodb.com/read.php?3,1196,1204
So, given that my table must have rows of approx 60,000 bytes each, is this a problem for innodb? Is it a big problem? deal breaker? what would you suggest?
Table structure: ID (int, autoinc, primary key), varchar(500), varchar(500)...repeat...varchar(500) until end of table reached