Last modified: 2006-11-21 16:47:07 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 2479 - Cache key names dependent on DB name
Cache key names dependent on DB name
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.7.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-21 21:01 UTC by Jamie Bliss
Modified: 2006-11-21 16:47 UTC (History)
0 users

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


Attachments

Description Jamie Bliss 2005-06-21 21:01:02 UTC
If you are using a form of caching other than DB (memc, Turck, or eAccelerator),
the keys are dependent on the DB name. So if you have 2 wikis using the same DB
(with different prefixes), then their cache keys will overlap.

This isn't a problem when using DB cache because it using the table prefix.

My proposal to fix it would be to add $wgCacheKeyPrefix to DefaultSettings.php,
which defaults to &$wgDBname, then change all current code to use that (Or just
change the BagOStuff classes to prefix it).
Comment 1 Brion Vibber 2005-06-21 21:25:07 UTC
Sensible thing would be to combine $wgDBname and $wgDBprefix.
Comment 2 Jamie Bliss 2006-05-27 05:14:00 UTC
Still a problem in ParserCache.php and in LinkCache.php.
Comment 3 Rob Church 2006-11-21 16:47:07 UTC
This was fixed in r16791.

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


Navigation
Links