Hi There,
(mysql, query) >From the online manual I see: -- innodb_data_file_path Paths to individual data files and their sizes. The full directory path to each data file is acquired by concatenating innodb_data_home_dir to the paths specified here. The file sizes are specified in megabytes, hence the 'M' after the size specification above. Do not set a file size bigger than 4000M, and on most operating systems not bigger than 2000M. InnoDB also understands the abbreviation 'G', 1G meaning 1024M. The sum of the sizes of the files must be at least 10 MB. -- This implies that I have to preguess how large each data file will be. Now, I understand with MyISAM tables that they just "grow" until they fill up your filesystem or hit some OS limit such as the 2Gb limit in Linux < 2.4.X. A few questions: 1) If I setup InnoDB with a 500Mb data file then suddenly run out of space could I: * seemlessly just stack another data file by adjusting my startup options * seemlessly just make the data file larger by changing the file size (i.e. don't add another datafile, just increase the file size) 2) Is there a way to make this more dynamic? * what if a user wants to add a 10Mb blob into my database, but the datafile has only 5Mb of space left for data... (with MyISAM tables they just seem to "grow" as needed) DSL -- Con te partiro, su navi per mari Che io lo so, no, no non esistono piu Con te io li vivro. (Sartori F, Quarantotto E) --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
