Hello Mediawiki-l,
thanks for the answer. I updated the database today (after the
2003-12-08 update) like this:
cd ...htdocs/wikipedia
wget http://download.wikipedia.org/archives/en/cur_table.sql.bz2
bzip2 -dc cur_table.sql.bz2 | mysql -u wikipedia -pmypassword wikipedia
Was that right, that easy? Or do I have to delete the old cur
table first? It seems it wasn't really updated. It took about 8
minutes (athlon 2400+/512mb ddr) and there was no error message.
When I now call pages from my local wikipedia mirror the most recent
edits are still from november. I looked up a page that was edited on
december 2 in wikipedia but on my local mirror only a version from
november appeared. (In november I installed everything the first time).
Also new entries are not accessable.
I only want to serve the printable page (via mod_rewrite) so
nobody ever will use the "What links here", "Related Pages" or
something like that. I understood your answer, Brion, that way
that under this circumstances I don't have to do a "php
rebuildlinks.php". Or should I? Does it really take several
hours?
But well, maybe its just something completey different...
thanks for your help!
--
Best regards,
Freerk mailto:freerk@gmx.net
Monday, December 8, 2003, 2:18:31 AM, you wrote:
BV> On Dec 7, 2003, at 12:56, Freerk wrote:
>> On
http://de.wikipedia.org/wiki/Wikipedia:Download and other
>> wikipedia download sites I found a tutorial on updating my local
>> database with the wikipedia mysql dump. It says afterwords you
>> have to do a "php rebuildlinks.php". But why? Well, I assume it
>> rebuilds some links but which ones? I thought everything is
>> dynamic in the database, and the only links are in the
>> cur_table, which I updated with a mysql command.
BV> There are presently three link tables:
BV> 'links' tracks all "live" links from wikipages to other wikipages that
BV> do exist;
BV> 'brokenlinks' tracks "broken" links, those that go to pages that don't
BV> yet exist;
BV> 'imagelinks' tracks usage of images in wikipages.
BV> There are a couple of uses for these tables:
BV> - enables "What links here" and "Related changes" to work, looking at
BV> incoming or outgoing links
BV> - provides the list of pages that use an image shown on an image's
BV> description page
BV> - allows making reports of pages that aren't linked (Orphans, Unused
BV> images) or are linked to but don't exist (Most wanted pages)
BV> - slightly speed up page rendering by avoiding individual checks for
BV> the existence of each linked page to determine how to render its link
BV> (The latest software also adds a 'linkscc' table which caches data from
BV> the other three tables. This is used only for speeding rendering.)
BV> If you import data to the cur table and don't rebuild the links, you
BV> won't be able to use "What links here", "Related changes", "Orphans",
BV> etc. If you don't want to, well I suppose that's okay...
BV> -- brion vibber (brion @ pobox.com)