user warning: Operand should contain 1 column(s) query: SELECT u.uid, xu.last_changed, xu.previously_changed, xu.priority_override, SUM(xur.priority) as priority, COALESCE(ua.dst) AS alias FROM druusers u LEFT JOIN druusers_roles ur ON u.uid = ur.uid LEFT JOIN druxmlsitemap_user_role xur ON ur.rid = xur.rid LEFT JOIN druxmlsitemap_user xu ON u.uid = xu.uid LEFT JOIN druurl_alias ua ON ua.src = CONCAT('user/', CAST(u.uid AS CHAR)) WHERE (xu.priority_override IS NULL OR xu.priority_override >= 0) AND u.uid <> 0 AND u.uid > 0 AND u.status <> 0 GROUP BY u.uid, xu.last_changed, xu.previously_changed, xu.priority_override HAVING COUNT(xu.priority_override) > 0 OR (SUM(xur.priority) IS NULL AND 0,5 <> -1 OR MIN(xur.priority) <> -1) in /srv/www/vhosts/jurtenland.eu/httpdocs/kohtenland/includes/database.mysql.inc on line 172.

this warning is still there, after writing or updating a node
i have made an upgrade from gstiemap to xmlsitemap

Comments

scoutladen’s picture

scoutladen commented

is there no solution anywhere out in the world?

jmoy’s picture

jmoy commented

The bad SQL is the fragment "0,5 <> -1" near the end. It appear because the number 0.5 is interpolated in a locale where decimal separator is a comma.

See this:
http://drupal.org/node/193214

But according to this comment, this should not be happening:
http://drupal.org/node/193214#comment-792329

Couldn't find any calls to setlocale in this module, so the culprit seems to be elsewhere.

picco’s picture

picco commented

i had a similar problem which was caused by a setlocale() call in my custom module. after removing the setlocale() call it was ok.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: user warning: Operand should contain 1 column(s) query » SQL error: operand should contain 1 column(s)
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Fixed

The XML Sitemap modules don't call setlocale(), so the problem is not caused by any of them.
I change the status to fixed because there isn't a status like bug is not caused by the module, or cannot reproduce it.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.