> In the meantime, you can work around the problem by
> implementing the GROUP BY function in your application
> code. Remove the aggregate functions and GROUP BY
> clause from your query and just return every row of
> the intermediate table, then compute the aggregates
> and grouping yourself. T
Joe Wilson <[EMAIL PROTECTED]> wrote:
>
> The old GROUP BY algorithm was extremely efficient whether or
> not the GROUP BY terms were indexable or not.
>
There were cases where the old algorithm performed
very, very poorly. You have found a case where the
new algorithm performs poorly, thoug
--- [EMAIL PROTECTED] wrote:
> > Joe Wilson <[EMAIL PROTECTED]> wrote:
> > > Anyone have any ideas how to speed up GROUP BY on huge views
> > > in recent versions of SQLite?
> > >
> > > http://www.sqlite.org/cvstrac/tktview?tn=1809
> > >
> > > The older versions of SQLite (prior to SQLite 3.2.6)
Joe Wilson <[EMAIL PROTECTED]> wrote:
> Anyone have any ideas how to speed up GROUP BY on huge views
> in recent versions of SQLite?
>
> http://www.sqlite.org/cvstrac/tktview?tn=1809
>
> The older versions of SQLite (prior to SQLite 3.2.6) used to
> perform GROUP BY operations in the main tab
Anyone have any ideas how to speed up GROUP BY on huge views
in recent versions of SQLite?
http://www.sqlite.org/cvstrac/tktview?tn=1809
The older versions of SQLite (prior to SQLite 3.2.6) used to
perform GROUP BY operations in the main table loop, grouping
rows as it went along. But the new
5 matches
Mail list logo