Last modified: 2007-08-28 16:01:26 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 11089 - WM-PA repeated db-error
WM-PA repeated db-error
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: shell
Depends on:
  Show dependency treegraph
Reported: 2007-08-28 02:02 UTC by Casey Brown
Modified: 2007-08-28 16:01 UTC (History)
0 users

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


Description Casey Brown 2007-08-28 02:02:32 UTC
If a vist page like "User talk:Cbrown1023", all is well... but if I try to visit "User:Cbrown1023", I get the following error:

Database error
A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was: 
(SQL query hidden)
from within function "LocalFile::loadFromDB". MySQL returned error "1054: Unknown column 'img_sha1' in 'field list' (".

I tried a few times and still got the same thing (I also checked dev log and didn't see anything that might affect this).
Comment 1 Brion Vibber 2007-08-28 16:01:26 UTC
The img_sha1 update hadn't been properly applied because the database was created in an intermediate state, so when combining updates it conflicted with a previously applied update.

Have fixed it, and did a sweep of other databases for the same problem; auditcomwiki also affected and fixed.

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