On 1/12/2015 10:37 AM, Dominique Devienne wrote:
OK, lets follow that logic:
1) a-comma yield just a (first row special case)
2) b-semi-colon yields semi-colon b
3) c-slash (both of them, collapsed by DISTINCT) yields slash c
4) c-colon yields colon c
5) d comma yields comma d
so that's "a;b/c:c,d", not "a;b:c/c,d"
Again, aggregate functions don't guarantee any particular order of
visiting the rows. In this example, the function happens to visit ':c'
first and '/c' second.
But I fail to see how the delimiter come from in "a;b:c/c,d", especially
why they are "out of order" vs the value-order. FWIW. --DD
Aggregate functions don't guarantee any particular order of visiting rows
within the group. What is this "value-order" of which you speak? I'm not
familiar with the term.
Just order of the "value" column in Clemens example.
What do you mean by "order of the "value" column"? The order in which
rows happened to be inserted into the table? Why should that order
matter for anything?
--
Igor Tandetnik
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
