Hi Martin, thanks for the corrections. I will list all the storage engines as we have a standard distribution.
Jan S Martin MC Brown wrote: >>> Which user will mysqld run as? root? So it reads /.my.cnf? Not the >>> best place for mysqld configuration ;-) > >> It can run as any user, but root is not a good choice :) > > Correction - it can run as any user *except root* (without special handling). > > The 'standard' is for a group of 'mysql' and a user of 'mysql'. The mysql > installation should be owned by the mysql group and the root user. The Mysql > data files should be owned by the mysql user. There are instructions on the > ownership in the INSTALL-BINARY and INSTALL-SOURCE files in the standard > distributions. > >>>> 3. Core Modules >>>> >>>> These are the proposed (statically linked) modules enabled by initial >>>> integration. >>>> >>>> MySQL server >>>> InnoDB - ACID storage engine >>>> MyIsam - non-ACID storage engine >>> Are the just ./configure time options or external modules? Is the >>> "statically linked" comment just a detail? Would anything be different >>> if they were dynamically linked? > >> I think I will rewrite this as the MySQL server has built in two (main) >> different storage engine, which you can choose for each table you >> create, where MyIsam is the default. > > Er, we have *way* more than two storage engines :) > > Standard 5.0 builds include MyISAM, InnoDB, Example, CSV, Blackhole, > Federated, Archive, Memory storage engines. The two primary choices are > InnoDB (transaqctions) and MyISAM (non-transactions), but many people will > make use of the other engines (the Memory and Archive storage engines for > example, are very popular in certain use-cases such as active caching and > logging respectively, especially when used within the webstack). > > I know we are not talking here about listing all of MySQL's capabilities, but > you might want to re-word that so that it doesn't look as if we are > explicitly excluding the other engine types (which you can do during > ./configure). > > MC > This message posted from opensolaris.org > > _______________________________________________ > webstack-discuss mailing list > webstack-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/webstack-discuss >
