Author: robchur
Description:
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.
Version: unspecified
Severity: enhancement
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T11326 Filter Special:Protectedpages by namespace | |||
| Resolved | None | T4171 Query page to list protected pages | |||
| Resolved | None | T4919 Protecting non-existent pages | |||
| Duplicate | None | T7986 Undeleting a page that was protected when deleted should cause it to be reprotected | |||
| Resolved | None | T6133 Feature request: page protection with expiry time | |||
| Resolved | None | T6145 Page restrictions should be moved to their own table |
robchur wrote:
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. ;-)
titoxd.wikimedia wrote:
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.
ayg wrote:
It's not fixed until it's in trunk. Plus, it's not even quite done in branch.