I'm not sure if this is a Rules error or Activity Log, but the error message references activity log tables, so I'm posting it here.

If I enable Grouping Messages by "Group by the acting user and the action performed" I get a SQL error saying:
-----------------
user warning: Truncated incorrect DOUBLE value: '8755,' query: UPDATE activity_log_messages SET aids = (aids + '8755,'), last_updated = 1325999033, cached = '' WHERE mid IN (7214) in C:\Program Files (x86)\Apache Software Foundation\Apache2.2\htdocs\modules\activity_log\activity_log.rules.inc on line 947.
user warning: Truncated incorrect DOUBLE value: '8755,' query: UPDATE activity_log_messages SET aids = (aids || '8755,'), last_updated = 1325999033, cached = '' WHERE mid IN (7214) in C:\Program Files (x86)\Apache Software Foundation\Apache2.2\htdocs\modules\activity_log\activity_log.rules.inc on line 954.
----------------------------------

This was done by uploading two images within the specified timeframe of the grouping. There is no error for uploading nodes that are not grouped.

Other information about the action settings is:
Entities in whose stream activity records ...: The taxonomy terms used in the node.....
The users who will be able to see this message: Everyone

Caching is disabled.

In displaying the message I see the English grouped message template, but not the Grouped item name.

Thanks for any tips to resolve this or any ideas for workarounds.

Comments

blairCruz’s picture

blairCruz commented

It looks like the issue is from the "," at the end of the (aids + '8755,'), if I remove this sql works. Looks like this sql is generated around line 945 of activity_log.rules.inc
SET aids = (aids + '%s'), last_updated = %d, cached = ''...

I'm not sure where the %s is assigned. I think this is the culprit but am unsure how to remove the trailing ","

icecreamyou’s picture

icecreamyou commented
Status: Active » Fixed

Committed fix to dev.

The error was actually because I forgot the "breaks" in a switch statement. As a result the code to update the grouped record ran 3 times with different syntaxes, and MySQL doesn't like the MSSQL or PostgreSQL syntax.

Status: Fixed » Closed (fixed)

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