That seems like an odd application of OVER (Partition by). Is there some performance reason one would want to do DISTINCT OVER (PARTITION BY) instead of a simple GROUP BY Sites.Customer, Sites.Digit, Count()?
On Fri, Apr 6, 2018 at 12:20 PM, Simon Slavin <slav...@bigfraud.org> wrote: > On 5 Apr 2018, at 11:41am, DThomas <d...@thomasres.net> wrote: > > > Select DISTINCT Sites.Customer, Sites.Digit, > > Count(TblContractTasks.TaskNumber) > > OVER (PARTITION BY Sites.Digit) As TaskCount > > FROM TblContractTasks INNER Join (Sites INNER Join TblContractDetails On > > Sites.Digit = TblContractDetails.SiteDigit) On > > TblContractTasks.ContractNumber = TblContractDetails.ContractNumber > > WHERE (Sites.Consultant='xx' ) ORDER BY Sites.Digit > > Instead of PARTITION BY use GROUP BY . See "with COUNT function" example > here: > > <http://www.sqlitetutorial.net/sqlite-group-by/> > > I think everything else used will continue to work. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
