Issue:DPL SQL Error and Illegal mix of collations

From FollowTheScore
Revision as of 07:40, 21 January 2009 by Bilardi (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Description: SQL error
Extension / Version: DPL   /   1.7.4
Type / Status: Bug   /   open

Problems with SQL errors

Hi all, I use mediawiki 1.13.1. I have got egual error as Dmb. I'm using

 {{#dpl:
 |category={{{category}}}
 |resultsheader=%PAGES%
 |noresultsheader=0
 |mode=userformat 
 }}

into gbrowse.org and here it is works. when I create egual template into other wiki it is not works and I have got this error:

The DPL extension (version 1.7.4) produced a SQL statement which lead to a Database error.
The reason may be an internal error of DPL or an error which you made,
especially when using DPL options like titleregexp.
Query text is:
SELECT DISTINCT `page`.page_namespace as page_namespace,`page`.page_title as page_title, REPLACE(REPLACE(CONCAT( IF(`page`.page_namespace=0, , CONCAT(CASE `page`.page_namespace WHEN 1 THEN 'Talk' WHEN 2 THEN 'User' WHEN 3 THEN 'User_talk' WHEN 4 THEN 'CRIBI_Genomics' WHEN 5 THEN 'CRIBI_Genomics_talk' WHEN 6 THEN 'Image' WHEN 7 THEN 'Image_talk' WHEN 8 THEN 'MediaWiki' WHEN 9 THEN 'MediaWiki_talk' WHEN 10 THEN 'Template' WHEN 11 THEN 'Template_talk' WHEN 12 THEN 'Help' WHEN 13 THEN 'Help_talk' WHEN 14 THEN 'Category' WHEN 15 THEN 'Category_talk' END, ':')), `page`.page_title), '_', ' '),'♣','⣣') as sortkey FROM `page` INNER JOIN `categorylinks` AS cl0 ON `page`.page_id=cl0.cl_from AND (cl0.cl_to='Grape_Genome_Team') WHERE 1=1 AND `page`.page_is_redirect=0 ORDER BY sortkey ASC LIMIT 0, 500

Error message is:
Illegal mix of collations (utf8_general_ci,COERCIBLE) and (latin1_bin,IMPLICIT) for operation 'concat' (localhost) 

If I log in wiki database mysql, and paste this query, it is works.. so I don't understand where it is the problem.. I don't find about built-in card suit symbol conversion line into DynamicPageList2.php script.

solution

Now it works in internal site with:

$wgDBmysql5 = false;