Hi all,
I tried to make a fresh install of MW 1.15rc1 on an empty InnoDB (latin1_swedish_ci) database, but to my surprise I see only MYISAM tables in the resulting database after the setup (see below).
How can that be? What am I missing?
// Rolf Lampa
archive MyISAM binary category MyISAM binary categorylinks MyISAM binary change_tag MyISAM binary externallinks MyISAM binary filearchive MyISAM binary hitcounter MEMORY latin1_swedish_ci image MyISAM binary imagelinks MyISAM binary interwiki MyISAM binary ipblocks MyISAM binary job MyISAM binary langlinks MyISAM binary logging MyISAM binary math MyISAM binary objectcache MyISAM binary oldimage MyISAM binary page MyISAM binary pagelinks MyISAM binary page_props MyISAM binary page_restrictions MyISAM binary protected_titles MyISAM binary querycache MyISAM binary querycachetwo MyISAM binary querycache_info MyISAM binary recentchanges MyISAM binary redirect MyISAM binary revision MyISAM binary searchindex MyISAM latin1_swedish_ci site_stats MyISAM binary tag_summary MyISAM binary templatelinks MyISAM binary text MyISAM binary trackbacks MyISAM binary transcache MyISAM binary updatelog MyISAM binary user MyISAM binary user_groups MyISAM binary user_newtalk MyISAM binary valid_tag MyISAM binary watchlist MyISAM binary -------------------------------------------- 41 tables latin1_swedish_ci
Hi!
I tried to make a fresh install of MW 1.15rc1 on an empty InnoDB (latin1_swedish_ci) database, but to my surprise I see only MYISAM tables in the resulting database after the setup (see below).
either you started MySQL with --skip-innodb, or InnoDB failed to start due to misconfiguration (check error log).
Domas
On Sun, Jun 7, 2009 at 1:29 PM, Domas Mituzas midom.lists@gmail.com wrote:
Hi!
I tried to make a fresh install of MW 1.15rc1 on an empty InnoDB (latin1_swedish_ci) database, but to my surprise I see only MYISAM tables in the resulting database after the setup (see below).
either you started MySQL with --skip-innodb, or InnoDB failed to start due to misconfiguration (check error log).
Shouldn't the installer complain if it has to use a different storage engine from the one selected?
Shouldn't the installer complain if it has to use a different storage engine from the one selected?
Lots of people would get complaints then. Lots of hosting providers don't have InnoDB enabled (for various strange reasons).
Domas
On Sun, Jun 7, 2009 at 3:01 PM, Domas Mituzas midom.lists@gmail.com wrote:
Shouldn't the installer complain if it has to use a different storage engine from the one selected?
Lots of people would get complaints then. Lots of hosting providers don't have InnoDB enabled (for various strange reasons).
Isn't that how it should be? If you select InnoDB at the installation screen (granted that it is the default) and it's not available, the installer should at least mention that it had to use MyISAM instead; it already blabs about what it's doing at each step and says plenty of things that could make people think something is wrong (diff3 not detected, ImageMagick not detected, etc.), so I don't think this would usher in a new raft of confused users.
Then again, maybe we should dodge the issue by only showing the storage engines that are available (we already do this for the object caching options, don't we?).
Domas Mituzas wrote:
I tried to make a fresh install of MW 1.15rc1 on an empty InnoDB (latin1_swedish_ci) database, but to my surprise I see only MYISAM tables in the resulting database after the setup (see below).
either you started MySQL with --skip-innodb, or ...
Now you're onto something... :) InnoDB was disabled in mysql\bin\my.cnf
Thank you for the hint!
// Rolf Lampa
mediawiki-l@lists.wikimedia.org