Skip to content
\n

This will return unique values for name_1156_20_group_concat, e.g. 8 concat strings in row 1. However, if I simply use

\n

(GROUP_CONCAT(?name_1156_20; SEPARATOR = \",\") AS ?name_1156_20_group_concat)

\n

It will only use distinct strings, e.g. only two for row 1.

\n

Simple question: Why does GROUP_CONCAT always uses DISTINCT? It doesn't matter if I use GROUP_CONCAT(DISTINCT ?name_1156_20; SEPARATOR = \",\") or GROUP_CONCAT(?name_1156_20; SEPARATOR = \",\"). I had expected a different behavior from specs:

\n
\n

All aggregates may have the DISTINCT keyword as the first token in their argument list. If this keyword is present then first argument to func is Distinct(M).

\n
","upvoteCount":1,"answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"

Should be fixed in v0.4.9

","upvoteCount":0,"url":"https://github.com/oxigraph/oxigraph/discussions/1205#discussioncomment-12441905"}}}

GROUP_CONCAT always DISTINCT ? #1205

Answered by Tpt
ch-sander asked this question in Q&A
Mar 9, 2025 · 1 comments · 1 reply
Discussion options

You must be logged in to vote

Should be fixed in v0.4.9

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@Tpt
Comment options

Tpt Mar 9, 2025
Maintainer

Answer selected by ch-sander
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants