wiki.techinc.nl/maintenance/archives/patch-querycache.sql

-- Used for caching expensive grouped queries

CREATE TABLE /*$wgDBprefix*/querycache (
  -- A key name, generally the base name of of the special page.
  qc_type char(32) NOT NULL,
  
  -- Some sort of stored value. Sizes, counts...
  qc_value int(5) unsigned NOT NULL default '0',
  
  -- Target namespace+title
  qc_namespace int NOT NULL default '0',
  qc_title char(255) binary NOT NULL default '',
  
  KEY (qc_type,qc_value)

) TYPE=InnoDB;
Replace ugly abuse of log pages to store cached results of query pages with a table that stores up to 1000 rows for each 'expensive' special page. This can be paged through, reducing the annoyingness of 50 result limits on the old system. Rebuilding the cache can be forced by adding "recache=1" URL parameter, but this will need to be refined with some sort of controls to prevent abuse. Added the user realname update to the installer's updater list, also. 2004-05-09 01:30:34 +00:00			`-- Used for caching expensive grouped queries`

added /$wgDBprefix/ in various places, to support upgrading from old prefixed databases, e.g. mine 2005-01-14 13:33:17 +00:00			`CREATE TABLE /$wgDBprefix/querycache (`
Use InnoDB by default for table creations if available. 2005-05-02 08:40:17 +00:00			`-- A key name, generally the base name of of the special page.`
Replace ugly abuse of log pages to store cached results of query pages with a table that stores up to 1000 rows for each 'expensive' special page. This can be paged through, reducing the annoyingness of 50 result limits on the old system. Rebuilding the cache can be forced by adding "recache=1" URL parameter, but this will need to be refined with some sort of controls to prevent abuse. Added the user realname update to the installer's updater list, also. 2004-05-09 01:30:34 +00:00			`qc_type char(32) NOT NULL,`
Use InnoDB by default for table creations if available. 2005-05-02 08:40:17 +00:00
			`-- Some sort of stored value. Sizes, counts...`
Replace ugly abuse of log pages to store cached results of query pages with a table that stores up to 1000 rows for each 'expensive' special page. This can be paged through, reducing the annoyingness of 50 result limits on the old system. Rebuilding the cache can be forced by adding "recache=1" URL parameter, but this will need to be refined with some sort of controls to prevent abuse. Added the user realname update to the installer's updater list, also. 2004-05-09 01:30:34 +00:00			`qc_value int(5) unsigned NOT NULL default '0',`
Use InnoDB by default for table creations if available. 2005-05-02 08:40:17 +00:00
			`-- Target namespace+title`
* (bug 719) Increase namespace fields from tinyint to regular int This keeps custom namespaces from bumping the 8-bit ceiling so quickly. 2005-05-02 10:15:02 +00:00			`qc_namespace int NOT NULL default '0',`
Replace ugly abuse of log pages to store cached results of query pages with a table that stores up to 1000 rows for each 'expensive' special page. This can be paged through, reducing the annoyingness of 50 result limits on the old system. Rebuilding the cache can be forced by adding "recache=1" URL parameter, but this will need to be refined with some sort of controls to prevent abuse. Added the user realname update to the installer's updater list, also. 2004-05-09 01:30:34 +00:00			`qc_title char(255) binary NOT NULL default '',`
Use InnoDB by default for table creations if available. 2005-05-02 08:40:17 +00:00
Replace ugly abuse of log pages to store cached results of query pages with a table that stores up to 1000 rows for each 'expensive' special page. This can be paged through, reducing the annoyingness of 50 result limits on the old system. Rebuilding the cache can be forced by adding "recache=1" URL parameter, but this will need to be refined with some sort of controls to prevent abuse. Added the user realname update to the installer's updater list, also. 2004-05-09 01:30:34 +00:00			`KEY (qc_type,qc_value)`
Use InnoDB by default for table creations if available. 2005-05-02 08:40:17 +00:00
put TYPE back in, now as it's back in 5.1 ;-) 2006-04-08 21:11:13 +00:00			`) TYPE=InnoDB;`