Last modified: 2009-12-16 15:43:04 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 T23748, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 21748 - Allow a configuration for disabling the page listing on Property namespace
Allow a configuration for disabling the page listing on Property namespace
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Markus Krötzsch
: patch, patch-need-review
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2009-12-03 11:09 UTC by Roi Avinoam
Modified: 2009-12-16 15:43 UTC (History)
0 users

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

Attachments
New $smwgPropertyPageShowList configuration directive (1.16 KB, patch)
2009-12-03 11:10 UTC, Roi Avinoam 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Roi Avinoam 2009-12-03 11:09:23 UTC 
On some over-populated properties, the page listing (showList()) on the Property namespace can trigger huge database queries that hang the application and DB. I've added a configuration for disabling this feature.
Comment 1 Roi Avinoam 2009-12-03 11:10:09 UTC 
Created attachment 6854 [details]
New $smwgPropertyPageShowList configuration directive
Comment 2 Markus Krötzsch 2009-12-10 15:58:45 UTC 
The patch would actually disable all listings (including subproperties) and it would also hide the property listings on Type pages and the element listings on Concept pages.

I have thus implemented a better solution: it is now possible to set the parameter $smwgPropertyPagingLimit to 0 for hiding the property page listings.

By the way: the query is just a simple DB lookup that is always limited to 25 results. It would be interesting to learn why it caused performance issues on your site at all. Retrieving 25 rows from a table is not really that challenging for a RDBMS even if the table is large.
Comment 3 Roi Avinoam 2009-12-16 15:43:04 UTC 
Even better! Thanks.

It's interesting why these queries are so time-consuming. I will look into it.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links