Last modified: 2007-06-05 00:52:34 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 9881 - $wgDBport for MySQL
$wgDBport for MySQL
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
PC All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-05-11 18:50 UTC by petr.bug
Modified: 2007-06-05 00:52 UTC (History)
1 user (show)

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


Description petr.bug 2007-05-11 18:50:36 UTC
In mediawiki-1.10.0 the option $wgDBport has no effect if $wgDBtype is "mysql".
Setting $wgDBport = "1234" (or any other value) has no offect on ability to
connect to database server.

$wgDBport was introduced for and used by Postgres since 1.7.
Comment 1 Rob Church 2007-05-11 18:53:50 UTC
That's right, $wgDBport is a PostgreSQL setting. To select a different port when
establishing a MySQL connection, use $wgDBserver = "hostname:port";
Comment 2 petr.bug 2007-05-11 19:23:39 UTC
I believed that it is not possible to specify port for MySQL. I was wrong. The
"hostname:port" works.

If $wgDBserver = "hostname:port"; can be used (what about IPv6 addresses?) for
MySQL then it may be possible for PostgreSQL code to use it as well. Thet would
deprecate $wgDBport and close this bug.
Comment 3 Rob Church 2007-06-05 00:52:34 UTC
The distinction is now made quite clear in LocalSettings.php and this is well documented. There's no bug here.

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