Last modified: 2007-01-10 23:42:43 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 T6145, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 4145 - Page restrictions should be moved to their own table
Page restrictions should be moved to their own table
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 2171 2919 4133 5986
  Show dependency treegraph
 
Reported: 2005-12-02 07:44 UTC by Rob Church
Modified: 2007-01-10 23:42 UTC (History)
1 user (show)

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


Attachments

Description Rob Church 2005-12-02 07:44:32 UTC
I propose moving the page restrictions field to its own table, which would
behave in a relational fashion, e.g. fields for protectionid(int11, pri,
auto-inc), userid(int 11), protected(int 1) etc.
Comment 1 Rob Church 2006-01-12 13:57:43 UTC
Wow, was I pissed when I wrote that schema? Anyway, still think this is
relevant. We'd want a field to correspond to the page_id, also, fields for edit
and move (corresponding to the names of groups required, obviously). Adding a
user field might be handy if we want to implement that suggestion to allow
preventing certain users from editing specific pages that's knocking around.

Indexing might be an idea, but indexes aren't my thing, so someone else can
suggest those. ;-)
Comment 2 Titoxd 2006-06-09 23:57:47 UTC
This could also be used to dynamically update [[Wikipedia:Protected pages]] (or
even better, create a new Special page, [[Special:Protectedlist]], akin to
[[Special:Ipblocklist]]). and it would also solve the problem of lazy sysops not
updating manual logs.
Comment 3 Titoxd 2007-01-10 06:08:34 UTC
Fixed in r19044, needs a branch merge and scap.
Comment 4 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-01-10 06:14:39 UTC
It's not fixed until it's in trunk.  Plus, it's not even quite done in branch.
Comment 5 Andrew Garrett 2007-01-10 23:42:43 UTC
Fixed in r19095.

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


Navigation
Links