On 31 May 2010 14:14, bawolff <bawolff...@gmail.com> wrote: > I'm going to use this message to respond to several people with this > email, hopefully it doesn't become confusing.
> Hmm, I like the idea of using the serialized blobs generally, and then > exposing some special few interesting properties into another table. I > was actually thinking that perhaps page_props could be used for this. > Currently all it contains is the hidden category listings (well and > theoretically any extension can house stuff there using > $wgPagePropLinkInvalidations, but i have yet to see an extension use > that, which is a little surprising as it seems like a wonderful way to > make really cool extensions really easily). Although it seems as if > that table is more meant for properties that change the behaviour of > the page they belong to in some way (like __HIDDENCAT__), any metadata > stored there would still be a "property", so I don't think thats too > abusing its purpose too much. Really there seems no reason to create a > new table if that one will do fine. [...] > I think the page_props table would be the best way to implement bug > 8298. Actually i was reading up on the page_props table the other day, > and I believe that in the commit implementing that table, bug 8298 was > given as an example of something cool the table could be used to > implement. I tried to use page_props once. I did end up using my own table, since the parser thinks it owns the page_props table and when page is parsed it happily deletes all values stored in page_props it doesn't know about. -Niklas -- Niklas Laxström _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
