Last modified: 2011-03-26 17:48:27 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 T30251, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 28251 - SQL error on trunk SocialProfile
SQL error on trunk SocialProfile
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
SocialProfile (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Jack Phoenix
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2011-03-26 13:43 UTC by Frozen Wind
Modified: 2011-03-26 17:48 UTC (History)
0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Frozen Wind 2011-03-26 13:43:50 UTC 
Example: http://fanon.clubpenguinwiki.info/wiki/User:Railfan1

The 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 "UserBoard::getUserBoardMessages". Database returned error "1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'OR (ub_user_id=543 AND ub_user_id_from=2) ) ORDER BY ub_id DESC LIMIT 10,0' at line 1 (mysql.clubpenguinwiki.info)".
Comment 1 Frozen Wind 2011-03-26 17:45:03 UTC 
Meh, updated trunk and it works.
Comment 2 Jack Phoenix 2011-03-26 17:48:27 UTC 
This was caused by r84617, which I've reverted in r84806.

To clarify, MediaWiki was generating invalid SQL, something like SELECT ... FROM user_board WHERE ub_type = '0' AND ub_user_id = something AND ( OR (ub_user_id=543 AND ub_user_id_from=2) ) ORDER BY ... -- it should have been just OR, without any useless ANDs. I don't know how to do that though, so I just ended up reverting the commit that broke it.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links