Database error on Special:Log [MySQL 4.1]
Closed, ResolvedPublic
Actions

Assigned To

None

Authored By

	• bzimport
	Dec 10 2004, 8:41 AM

Description

Author: binesh-dated-1103272636.ad746d

Description:
I get this when I go to my Special:Log...

A database query syntax error has occurred. This may indicate a bug in the
software. The last attempted database query was:

SELECT log_type, log_action, log_timestamp, log_user, user_name,

log_namespace, log_title, cur_id, log_comment FROM user, logging LEFT OUTER JOIN
cur ON log_namespace=cur_namespace AND log_title=cur_title WHERE
user_id=log_user ORDER BY log_timestamp DESC LIMIT 0,50

from within function "". MySQL returned error "1267: Illegal mix of collations
(latin1_swedish_ci,IMPLICIT) and (latin1_bin,IMPLICIT) for operation '='".

I'm running the following:

MediaWiki (http://wikipedia.sf.net/): 1.4beta2 
PHP (http://www.php.net/): 4.3.9 (apache) 
MySQL (http://www.mysql.com/): 4.1.7

(I'm also using Apache 1.3.33, if that matters any)

Unfortunately, I have no other info to give... It sort of is that simple tho...
If I just go to the log page, that's what I get.

Version: 1.4.x
Severity: normal
OS: Linux
Platform: PC

Details

Reference: bz1057

	Title	Reference	Author	Source Branch	Dest Branch
	Update README.md	repos/mediawiki/services/ipoid!66	stran	update-readme	main

Customize query in GitLab

Event Timeline

• bzimport raised the priority of this task from to Medium.Nov 21 2014, 8:07 PM

• bzimport added a project: MediaWiki-Special-pages.

• bzimport set Reference to bz1057.

• bzimport added a subscriber: Unknown Object (MLST).

• bzimport created this task.Dec 10 2004, 8:41 AM

Ah, the joys of MySQL 4.1. :P

Having built for older versions, our table definitions don't specify collations or
character sets. I'm not sure what exactly we'll need to change, and under what
circumstances it's a problem... Just for some extra background: is this a fresh
installation of MediaWiki, or an upgrade? Is it a fresh installation of MySQL 4.1,
or an upgrade from an earlier version of MySQL?

binesh-dated-1103272636.ad746d wrote:

(In reply to comment #1)

Just for some extra background: is this a fresh
installation of MediaWiki, or an upgrade? Is it a fresh installation of MySQL

4.1,

or an upgrade from an earlier version of MySQL?

It never was an existing MediaWiki 1.3.8, if that's what you mean. (I started
from MediaWiki 1.4beta1 (which still had the problem) and then moved to beta2.

As for MySQL, I was always on 4.1...

binesh-dated-1103272636.ad746d wrote:

I just tested it on another box, with a fresh install of

*MediaWiki (http://wikipedia.sf.net/): 1.4beta2
*PHP (http://www.php.net/): 5.0.2 (apache)
*MySQL (http://www.mysql.com/): 4.1.7

And, it had the same problem...

paul wrote:

Running MySQL 4.1.8 gcc built binaries, along with PHP 5.0.3 with both mysql and
mysqli configuration, MediaWiki seems to be working perfectly expect when
accessing Special:Log. I get the same error as above, a brand new installation
of 1.4 beta 6.

--Paul Laudanski
http://castlecops.com

paul wrote:

In addition to Special:Log causing this error, Special:Log/delete brings it up
as well. Is the Special:Log call the only one affected by this?

Created attachment 272
Column format change which may fix this [HEAD]

The problem seems to be that log_title is not specified as binary, whereas
cur_title/page_title is. MySQL 4.0 doesn't care, but MySQL 4.1 won't let you
join on those two fields (which the log display does) as it's interpreted their
encodings differently.

Attached is a patch which changes the column definition and adds updaters to
change it in place. The updaters.inc fixes don't patch cleanly against REL1_4;
it would be easy to manually copy in, or you can just run
maintenance/archives/patch-logging-table.sql manually.

I haven't checked this in as I don't have a 4.1 test box set up at the moment
so can't confirm that it does the job, or whether the change in place is
sufficient on an already running 4.1 db. (It may require dropping and
recreating the table, depending on how the charset comes into things and when
and how it's set. If the wrong charset 'sticks' on the alter it might requiring
recreating the table, or else being more specific in the alteration.)

Attached:

logging-fix.diff2 KBDownload

Tested successfully on MySQL 4.1, committed to 1.4 branch. Had already put into HEAD.

Bug 1742 has been marked as a duplicate of this bug. ***

	F1759: logging-fix.diff
	Nov 21 2014, 8:07 PM

Database error on Special:Log [MySQL 4.1]Closed, ResolvedPublicActions

Description

Details

Event Timeline

Database error on Special:Log [MySQL 4.1]
Closed, ResolvedPublic
Actions