Might be column indexing have restriction over number of columns to be
indexed, but for number of columns, hope you can overrider with the
"avg_row_length" and "max_rows" during create/alter table.
The length/size of the table depends on the file system(maximum file size
defined by the OS). Try giving maximum value for avg_row_length.
ViSolve DB Team
----- Original Message -----
From: "Fabian Köhler" <fab@stripped>
Sent: Tuesday, April 17, 2007 4:34 AM
Subject: Max columns in a tabel in MyISAM storage engine
> i have table with answers to questions. Every answer is a column in the
> table. i.e.
> another option to save it would be sth like this:
> The last one is not really useable when working with large amounts of
> data, when you want to select i.e. 200 questions with answers it's 200*nof
> answers queries to get them.
> The problem with the first solution is, that MyISAM storage engine is
> limited to 2599 columns i think. So what's happening if i have more
> answers than columns available?
> Does anybody have an idea? VIEWs or GROUP_CONCAT doesn't seem to be an
> option, they are all to slow. What's the "right" way to store and select
> such information?
> Thank you very much.
> Fabian Köhler http://www.fabiankoehler.de
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 269.4.0/762 - Release Date: 4/15/2007
> 4:22 PM