Eoghan Bonass
05/26/2025, 10:33 AMEoghan Bonass
05/26/2025, 10:34 AMEoghan Bonass
05/26/2025, 10:35 AMEoghan Bonass
05/26/2025, 10:35 AM{
"title": "Bad Request",
"status": 400,
"detail": "An error has occurred while calculating the result",
"resultId": "9c4942fe2e71176dc981e2ec3162e8a0ad948575",
"reason": "General error",
"traceId": "78b7c640f22bfd305c1a0b525746bbe3"
}
Eoghan Bonass
05/26/2025, 10:36 AM/debug
approach to extract the underlying SQL generated for this query:
SELECT "a_label_project_fields_43161a5d21cd42cca74526a3_350ac179c9badd" AS "a_label_project_fields_43161a5d21cd42cca74526a3_fbf5f9953e2cf3", 1 AS "m_1"
FROM (
SELECT "project_status" AS "a_label_project_fields_43161a5d21cd42cca74526a3_350ac179c9badd"
FROM "wksp_{wksp_id}"."project_fields_43161a5d21cd42cca74526a3c4a5cdd0"
GROUP BY "project_status"
) AS "t1"
WHERE "a_label_project_fields_43161a5d21cd42cca74526a3_350ac179c9badd" = ('On Hold ' || CHR(STRTOL('d83d', 16)::INT) || CHR(STRTOL('dfe1', 16)::INT));
Eoghan Bonass
05/26/2025, 10:37 AMEoghan Bonass
05/26/2025, 10:39 AM('On Hold ' || CHR(STRTOL('d83d', 16)::INT) || CHR(STRTOL('dfe1', 16)::INT))
portion seems to be the root cause.
When I try to run just this portion directly in our Redshift db, i.e:
SELECT 'On Hold ' || CHR(STRTOL('d83d', 16)::INT) || CHR(STRTOL('dfe1', 16)::INT);
It returns a unicode error:
ERROR: invalid unicode codepoint
Eoghan Bonass
05/26/2025, 10:41 AMMauricio Cabezas
05/26/2025, 3:32 PMActive <unicode?>
On hold <🟡>Could you please confirm, I can see 'd83d' but I would like to confirm?
Eoghan Bonass
05/27/2025, 8:37 AMMauricio Cabezas
05/27/2025, 1:29 PMEoghan Bonass
05/27/2025, 1:48 PM