Last modified: 2014-05-06 02:12:24 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 T56959, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 54959 - Table 'wikidatawiki_p.user' doesn't exist
Table 'wikidatawiki_p.user' doesn't exist
Status: RESOLVED FIXED
Product: Wikimedia Labs
Classification: Unclassified
tools (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Marc A. Pelletier
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-04 08:49 UTC by Liangent
Modified: 2014-05-06 02:12 UTC (History)
3 users (show)

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


Attachments

Description Liangent 2013-10-04 08:49:24 UTC
A database query syntax error has occurred.
The last attempted database query was:
"SELECT  rev_id,rev_page,rev_text_id,rev_timestamp,rev_comment,rev_user_text,rev_user,rev_minor_edit,rev_deleted,rev_len,rev_parent_id,rev_sha1,page_namespace,page_title,page_id,page_latest,page_is_redirect,page_len,user_name  FROM `wikidatawiki_p`.`revision_userindex` INNER JOIN `wikidatawiki_p`.`page` ON ((page_id = rev_page)) LEFT JOIN `wikidatawiki_p`.`user` ON ((rev_user != 0) AND (user_id = rev_user))  WHERE page_namespace = '2' AND page_title = 'Liangent-bot/message/ts-wblinktitles-conflict-item' AND (rev_id=page_latest)  LIMIT 1  "
from within function "Revision::fetchFromConds".
Database returned error "1146: Table 'wikidatawiki_p.user' doesn't exist (wikidatawiki.labsdb)"
Comment 1 Marc A. Pelletier 2013-10-04 13:02:34 UTC
Some user tables have been temporarily removed pending the completion of our security audit and should return shortly.

Sorry for the inconvenience.
Comment 2 Bartosz Dziewoński 2013-10-04 13:04:15 UTC
(For posterity: the audit is most likely related to bug 54847.)
Comment 3 Marc A. Pelletier 2014-05-06 02:12:24 UTC
Long since resolved.

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


Navigation
Links