Events page 500 on PostgreSQL: getEventDataEvents no-event branch missing GROUP BY (42803)

[PeterUstinox]

Describe the bug

On a PostgreSQL-backed instance, the website Events page renders "Something went wrong". The request GET /api/websites/{id}/event-data/events (issued with no specific event selected) returns 500 with:

ERROR: column "website_event.event_name" must appear in the GROUP BY clause or be used in an aggregate function (SQLSTATE 42803)

Root cause

In src/queries/sql/events/getEventDataEvents.ts, the relational (Prisma) no-event branch selects count(*) alongside three non-aggregated columns but has no GROUP BY:

select
  website_event.event_name as "eventName",
  event_data.data_key as "propertyName",
  event_data.data_type as "dataType",
  count(*) as "total"
from event_data
inner join website_event
  on website_event.event_id = event_data.website_event_id
where event_data.website_id = {{websiteId::uuid}}
  and event_data.created_at between {{startDate}} and {{endDate}}
limit 500

The ClickHouse no-event branch in the same file does group (group by event_data.data_key, event_data.data_type, event_data.event_name), and the event-filtered relational branch has its own group by. So this only bites SQL backends: PostgreSQL always, MySQL with ONLY_FULL_GROUP_BY.

Verified directly against PostgreSQL 16 by running the exact shipped query.

Affected versions

3.2.0 and earlier 3.x. The same branch is still missing the GROUP BY on current master.

(Distinct from #3732, which was the WHERE-clause 42601 issue and is fixed.)

Suggested fix

Add the GROUP BY to the relational no-event branch, mirroring the other branches:

...
${filterQuery}
group by website_event.event_name, event_data.data_key, event_data.data_type
limit 500

Environment

• umami 3.2.0 (Docker, ghcr.io/umami-software/umami:latest)
• PostgreSQL 16

[Jkarntzen]

Confirmed on 3.2.0 as well (Azure Database for PostgreSQL Flexible Server 16, self-hosted via container image ghcr.io/umami-software/umami:3.2.0).

Same symptom and root cause as described: GET /api/websites/{id}/event-data/events (no event param) returns 500 with SQLSTATE 42803, and the no-event branch in src/queries/sql/events/getEventDataEvents.ts is still missing the GROUP BY on current master. The event-filtered branch (which has the proper GROUP BY) works fine.

Adding group by website_event.event_name, event_data.data_key, event_data.data_type to the no-event branch fixes it locally.

[ancashoria]

so many issues with Umami 3.2.0. I'm glad I backed up my db before the update

[franciscao633]

PR is merged. We will do a hotfix patch later as we resolve more bugs.