Jamie Lawrie
04/18/2024, 4:26 AMJamie Lawrie
04/18/2024, 4:26 AMSELECT count({label/CURRENT_SERVICE_EDUCATORS_GD.USER_ID})
Jamie Lawrie
04/18/2024, 4:28 AMSELECT COUNT(DISTINCT USER_ID) as UNIQUE_USERS
FROM current_service_educators_gd
Jamie Lawrie
04/18/2024, 4:28 AMJamie Lawrie
04/18/2024, 4:28 AMJamie Lawrie
04/18/2024, 4:29 AMJamie Lawrie
04/18/2024, 4:31 AMSELECT "m_d57f747f246d7b3ce3ed53709c95bfd9" AS "m_1"
FROM (SELECT COUNT("CURRENT_SERVICE_EDUCATORS_GD"."USER_ID") AS "m_d57f747f246d7b3ce3ed53709c95bfd9", TRUE AS "def_m_d57f747f246d7b3ce3ed53709c95bfd9"
FROM "GOODDATA"."CURRENT_SERVICE_EDUCATORS_GD"
INNER JOIN "GOODDATA"."ALL_SERVICES" ON "CURRENT_SERVICE_EDUCATORS_GD"."SERVICE_ID" = "ALL_SERVICES"."SERVICE_ID"
WHERE "ALL_SERVICES"."UNIQUE_SERVICE_NAME" IN ({LIST OF SERVICES REDACTED})
GROUP BY CAST(NULL AS INTEGER)) AS "t2"
WHERE "t2"."def_m_d57f747f246d7b3ce3ed53709c95bfd9"
Jamie Lawrie
04/18/2024, 4:32 AMJamie Lawrie
04/18/2024, 4:37 AMSELECT COUNT("CURRENT_SERVICE_EDUCATORS_GD"."USER_ID")
in particular - surely if count always behaves as unique count it should always be a distinct count?Jamie Lawrie
04/18/2024, 4:37 AMJamie Lawrie
04/18/2024, 4:38 AMJamie Lawrie
04/18/2024, 4:39 AMJamie Lawrie
04/18/2024, 4:47 AMJamie Lawrie
04/18/2024, 4:49 AMSELECT "m_9247d7c0652127f5e523386f63d9f023" AS "m_1"
FROM (SELECT COUNT("USER_ID") AS "m_9247d7c0652127f5e523386f63d9f023", TRUE AS "def_m_9247d7c0652127f5e523386f63d9f023"
FROM "GOODDATA"."CURRENT_SERVICE_EDUCATORS_GD"
GROUP BY CAST(NULL AS INTEGER)) AS "t1"
WHERE "def_m_9247d7c0652127f5e523386f63d9f023"
It seems very clearly to be failing to apply a distinct countMarcel van Vliet
04/18/2024, 4:54 AMMarcel van Vliet
04/18/2024, 4:55 AMJamie Lawrie
04/18/2024, 4:55 AMJamie Lawrie
04/18/2024, 5:14 AMSELECT COUNT({label/CURRENT_SERVICE_EDUCATORS_GD.USER_ID}) USING {dataset/CURRENT_SERVICE_EDUCATORS_GD}
with the expectation that this will tell it to count the users on the actual educators tableJamie Lawrie
04/18/2024, 5:16 AMJamie Lawrie
04/18/2024, 5:24 AMJamie Lawrie
04/18/2024, 5:25 AMJamie Lawrie
04/18/2024, 6:05 AMMichal Hauzírek
04/18/2024, 6:39 AMJamie Lawrie
04/18/2024, 8:15 PMMichal Hauzírek
04/19/2024, 10:33 PM