Login | Register
Table of Contents [+/-]
I'd like to understand why the storing of the data is a machine and OS independent. I know that Intel Machines stores data in RAM with the high byte first viceversa Motorola Machines stores data with the low one. Andrea
Maximum key length is 500 bytes by default (can be changed by recompiling). In cases of keys longer than 250 bytes, a bigger key block size than the default of 1024 bytes is used for this key. how can i recompile to enlarge maximum key length???i want to create table like this...create table test( field1 text not null,primary key(field1(1024)) )that is, i want primary key length to be more than 1024...answer me... plz...ASAP
i think the documentation for this section should contain an overview on MyISAM tables which can give better idea of their usage. something similar to InnoDB tables overview
"Note that index files are usually much smaller with MyISAM than with ISAM. This means that MyISAM will normally use less system resources than ISAM, but will need more CPU time when inserting data into a compressed index."Shouldn't the index be uncompressed for MyISAM as that would make it faster. I dont think disk space is much of a concern for me on a server, especially if it is few KB or MB.
Tommy - The data, however, must be read from the the disk. Disk reads are very slow. The less data read from the disk, the better. A few CPU cycles to [de]compress pales in comparison to the extra data being transfered to/from disk.
> "Maximum number of keys/table is 32 as default. This can be enlarged to 64 without having to recompile myisamchk."Hm, how? I did not find any hint in the documentation and as far as I checked, the mailing lists also contained nothing about this.I must admit, instead of asking a question here, I've wanted to post a msg on the public mailing list for documentation but I'm too stupid to find a way to post a msg - there's no mail address, no posting form and no hint in the FAQ.
Add your own comment.