Steps to reproduce:
* install views, views_ui, and field_ui
* create a content type with a file field
* create a view and FIRST add the file field to it
* NEXT switch on aggregation in the advanced settings.
The view now generates broken SQL, by trying to select a non-existent node__{field_id}.{field_id]_ column for grouping.
The broken state is only reached by enabling aggregation after the field is already created. Adding the field after aggregation is enabled will initialise the column correctly, and saving the aggregation settings at least once will fix the problem.
Comments
Comment #2
cburschkaComment #3
roam2345 commentedBump
Comment #4
lendudeThis is a duplicate of #2815881: Switching on aggregation generates fatal "Column not found: 1054 Unknown column" SQL error when using multi-column Fields please try the patch there and see if it helps.