Last modified: 2010-05-15 15:42:46 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T10398, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 8398 - MySQL 5 (strict mode) not detected during installation
MySQL 5 (strict mode) not detected during installation
Status: RESOLVED DUPLICATE of bug 7669
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
1.8.x
PC Windows XP
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://www.mwusers.com/forums/showthr...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-12-27 09:35 UTC by emddudley
Modified: 2010-05-15 15:42 UTC (History)
0 users

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


Attachments

Description emddudley 2006-12-27 09:35:32 UTC
Installation fails with no error message for MediaWiki 1.8.2 on a Windows XP
system with Apache 2.2.3, PHP 5.2.0, and MySQL 5.0.27.

Last item on the installation screen is:

Creating tables... using MySQL 4 table defs...Query "long query was here" failed
with error code "BLOB/TEXT column 'user_password' can't have a default value
(localhost)

(query omitted for brevity)

Two problems: The installer detected MySQL 4 instead of 5, and it choked on
default values in the query.

There are two work-arounds, one of which is described at the provided URL (it
involves modifying the installer query to remove the default values). The other
is to disable MySQL strict mode.
Comment 1 Brion Vibber 2006-12-27 09:38:06 UTC

*** This bug has been marked as a duplicate of 7669 ***
Comment 2 Rob Church 2006-12-27 09:40:52 UTC
I'd just like to briefly point out that MediaWiki didn't detect MySQL 4, per se;
rather, it used MySQL 4 table definitions, because you selected
"backwards-compatible UTF-8 handling" in the installer (or failed to select the
experimental mode). This is actually nothing to worry about.

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


Navigation
Links