Jonathan Walther wrote: That's how I did it in Phase II. Did work, but this works better. And, namespaces are currently *not* part of the title in the database! Magnus

Jonathan Walther wrote: OK, we can change that, *once* we've switched to Postgres... It's no table, it is in Language.php... Yes! How else to tell apart [[Vulture]] and [[user:Vulture]]? And where to talk? etc. Magnus

Yes, Wikipedia is a namespace, as are Wikipedia talk, Image and Image talk. I'm not 100% sure about Special, though - there are no 'real' pages in there, just query results. Andre Engels

On Tue, Nov 19, 2002 at 11:26:09AM +0100, Jens Frank wrote: Au contraire. I believe the code would become more simple and readable. Notice I never suggested "a table per namespace". I suggested only the 6 tables that covered every circumstance I could think of. And there are already a lot of queries; having less queries and making of them refer to a slightly different set of tables doesn't strike me as in any way complicating things. The complication comes when you shoehorn different things into the same table. My question remains, do we need namespaces for any other reason than to know whether the row represents an article, binary, or discussion? Jonathan -- Geek House Productions, Ltd. Providing Unix & Internet Contracting and Consulting, QA Testing, Technical Documentation, Systems Design & Implementation, General Programming, E-commerce, Web & Mail Services since 1998 Phone: 604-435-1205 Email: djw(a)reactor-core.org Webpage: http://reactor-core.org Address: 2459 E 41st Ave, Vancouver, BC V5R2W2

On Die, 2002-11-19 at 11:24, Jonathan Walther wrote: As has already been noted, namespaces are also used for User pages and Wikipedia-specific pages. I don't think there's much sense in splitting stuff up into separate tables, or adding these types of pages as properties (how is that cleaner than what we have now?). As for storing binaries in tables, this is not desirable with our current config (table is already too big), and probably not desirable with PostgreSQL (we only have your word on performance, and having them as files has various advantages). Having the names of the namespaces in the code may not look very clean, but it actually is, because we need them in various translations ("Talk" is called "Diskussion" in the German WP etc.), and it's better to have all localization stuff in one place (Language*.php). If this is properly documented, I don't see a problem. Can we stick to the "if it's not broken, don't fix it" rule? If you want to work on mod_wiki, I think it would be better to do it on a separate mailing list (I'd actually be interested in that). If you want to help with the PostgreSQL port of Wikipedia, we should focus on the table structure, fulltext search, MySQLisms etc. It would probably be the most efficient for one PostgreSQL expert to just convert everything that's necessary and then put the code+db dump somewhere, then we can work on a conversion script. Other than that, we have many urgent issues, like fixing the current IP blocking mechanism and giving sysops better tools to restore vandalized pages. Regards, Erik -- FOKUS - Fraunhofer Insitute for Open Communication Systems Project BerliOS - http://www.berlios.de

On Tue, Nov 19, 2002 at 12:56:18PM +0100, Magnus Manske wrote: Thanks for the enumeration, Magnus. It is very helpful. Could you tell me, how are Wikipedia namespace articles different from regular articles? Are they special in that only sysops can edit them? Are they special in that what is in them results in changes being made to the database and the behavior of the Wikipedia? That is what I'm exploring here. Jonathan -- Geek House Productions, Ltd. Providing Unix & Internet Contracting and Consulting, QA Testing, Technical Documentation, Systems Design & Implementation, General Programming, E-commerce, Web & Mail Services since 1998 Phone: 604-435-1205 Email: djw(a)reactor-core.org Webpage: http://reactor-core.org Address: 2459 E 41st Ave, Vancouver, BC V5R2W2