Last modified: 2010-05-15 16:03:43 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 13586 - ENGINE vs TYPE
ENGINE vs TYPE
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
1.13.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-04-02 00:04 UTC by Huji
Modified: 2010-05-15 16:03 UTC (History)
1 user (show)

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


Attachments

Description Huji 2008-04-02 00:04:24 UTC
Some of the sql statements (like maintenance/tables.sql or extensins/Oversight/hidden.sql) are using TYPE attribute; this throws a notice on most recent versions of MySQL:

'TYPE=storage_engine' is deprecated; use 'ENGINE=storage_engine' instead

Is there a reason for not using ENGINE instead of TYPE?
Comment 1 Robert Leverington 2008-04-02 10:28:28 UTC
Is "ENGINE" available in MySQL 4.0? We currently support back to that version (it is indeed the one running on Wikimedia) and there currently is no reason to upgrade; even though there would be more features, performance would be significantly reduced.
Comment 2 Brion Vibber 2008-04-02 17:56:31 UTC
ENGINE is not available in some older versions of MySQL 4.0.

Currently, we use ENGINE for the MySQL 5 schema modes and TYPE for the MySQL 4 schema mode. (You can see this in the installer, where it sets up $wgDBTableOptions.)

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


Navigation
Links