dm-aggregates doesn't support DISTINCT
Reported by Aaron Qian | September 13th, 2008 @ 07:30 PM
dm-aggregates doesn't support the use of COUNT(DISTINCT id) type of SQL statements.
Daniel Goh has a pretty good patch that fixes this problem:
Comments and changes to this ticket
-
Dan Kubb (dkubb) December 5th, 2008 @ 04:13 AM
- Assigned user cleared.
- State changed from “new” to “hold”
Aaron, I've reviewed the patch and I wonder if this is really what we want: when unique is true to make all the aggregate functions use DISTINCT. Maybe I don't understand DISTINCT in that context (I rarely use it), but can you think of any issues it will cause?
I'd be more than happy to apply this if you'd explain what the difference is, and if it'll cause any issues.
Also, I've updated Daniel Goh's patch with the latest dm-more, and attached it to this ticket.
-
Dan Kubb (dkubb) January 8th, 2009 @ 02:50 PM
- Assigned user set to “Dan Kubb (dkubb)”
-
Dan Kubb (dkubb) June 7th, 2009 @ 03:54 AM
- State changed from “hold” to “not-applicable”
I am going to close this ticket. More information as requested on December 5th with no reply. Currently I do not want to use DISTINCT until I have a valid use case for including it in dm-aggregates.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Dan Kubb (dkubb)