Last modified: 2010-05-15 15:37:39 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 10040 - installation error mysql
installation error mysql
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
PC Windows XP
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-05-27 10:35 UTC by xshape
Modified: 2010-05-15 15:37 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description xshape 2007-05-27 10:35:52 UTC
* PHP 5.1.4: ok
    * PHP server API is cgi-fcgi; using ugly URLs (index.php?title=Page_Title)
    * Have XML / Latin1-UTF-8 conversion support.
    * PHP is configured with no memory_limit.
    * Have zlib support; enabling output compression.
    * Neither Turck MMCache nor eAccelerator are installed, can't use object caching functions
    * GNU diff3 not found.
    * Found GD graphics library built-in, image thumbnailing will be enabled if you enable uploads.
    * Installation directory: D:\showroom\joomla\components\com_mambowiki
    * Script URI path: /showroom/joomla/components/com_mambowiki
    * Connecting to joomla on localhost as root...success.
    * Connected to 5.0.27-community-nt; using enhancements for mySQL 4.
      Current directory is D:\showroom\joomla\components\com_mambowiki\config
    * Creating tables... using MySQL 3/4 table defs...Query "CREATE TABLE wiki_user ( user_id int(5) unsigned NOT NULL auto_increment, user_name varchar(255) binary NOT NULL default '', user_real_name varchar(255) binary NOT NULL default '', user_password tinyblob NOT NULL default '', user_newpassword tinyblob NOT NULL default '', user_email tinytext NOT NULL default '', user_options blob NOT NULL default '', user_touched char(14) binary NOT NULL default '', user_token char(32) binary NOT NULL default '', user_email_authenticated CHAR(14) BINARY, user_email_token CHAR(32) BINARY, user_email_token_expires CHAR(14) BINARY, PRIMARY KEY user_id (user_id), UNIQUE INDEX user_name (user_name), INDEX (user_email_token) ) TYPE=InnoDB" failed with error code "BLOB/TEXT column 'user_password' can't have a default value".
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-05-27 18:02:22 UTC
As far as I'm aware, this was fixed some time ago in 1.9 or 1.10.  Please reopen if you can reproduce in 1.10 (or better yet, trunk).

As a workaround, you can either disable MySQL strict mode in your configuration file or manually alter tables.sql to remove the default values for columns that cannot have them.

Note You need to log in before you can comment on or make changes to this bug.