Last modified: 2011-01-05 09:51:34 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 T28552, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 26552 - ForeignDBRepo broken?
ForeignDBRepo broken?
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
1.17.x
All All
: High critical (vote)
: ---
Assigned To: Sam Reed (reedy)
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-01-03 15:37 UTC by Gregor Hagedorn
Modified: 2011-01-05 09:51 UTC (History)
4 users (show)

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


Attachments

Description Gregor Hagedorn 2011-01-03 15:37:00 UTC
As well as connecting to WikimediaCommons by ForeignAPIRepo (working ok) we also connect to a local shared image repository using ForeignDBRepo. While working in a previous version (r69050), the ForeignDBRepo in the current 1.18alpha (r79256) fails with the message (when connecting to a repo with db name openmedia):

„1146: Table 'openmedia.16page' doesn't exist (localhost:PORT)“.

Maintenance/update.php worked ok. I cannot find information about a mediawiki table named 16. Any clues?

With $wgShowSQLErrors = true; the following is shown:

SELECT page_id FROM `16page` WHERE page_namespace = '6' AND page_title = 'zzzzzzz.jpg' LIMIT 1 

Function „LocalRepo::getArticleID“.
Comment 1 Gregor Hagedorn 2011-01-03 16:59:23 UTC
Further testing of svn revs revealed that the error is yet absent in r75380 but present in r75400
Comment 2 Gregor Hagedorn 2011-01-03 17:17:49 UTC
Sorry, correction to the above: r75300 is ok, but already r75350 is broken (claimed 75380 still wrongly claimed ok in previous comment).
Comment 3 Bryan Tong Minh 2011-01-03 21:38:47 UTC
Could you check if r75340 is ok?
Comment 4 Bryan Tong Minh 2011-01-03 21:41:24 UTC
Found it, r75343.
Comment 5 Sam Reed (reedy) 2011-01-04 19:34:22 UTC
Right, simplest possible "fix" for this is r79591

It will fix the errors you're getting, but I'm leaving this bug open while I hunt around for other instances of this...
Comment 6 Sam Reed (reedy) 2011-01-04 20:53:06 UTC
r79595, r79593
Comment 7 Gregor Hagedorn 2011-01-05 09:51:34 UTC
I confirm that our problems are solved with r79596!

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


Navigation
Links