s
will be identical; but the contents reflect the last record read if the
statement requires a sort operation).
-Ursprüngliche Nachricht-
Von: Dominique Devienne [mailto:ddevie...@gmail.com]
Gesendet: Mittwoch, 27. November 2013 09:45
An: General Discussion of SQLite Database
Betreff
On Wed, Nov 27, 2013 at 9:35 AM, Clemens Ladisch wrote:
> veeresh kumar wrote:
> > I see that in release history for 3.8.1 below item.
> > "Estimate the sizes of table and index rows and use the smallest
> applicable B-Tree for full scans and "count(*)" operations."
> >
> >
veeresh kumar wrote:
> I see that in release history for 3.8.1 below item.
> "Estimate the sizes of table and index rows and use the smallest applicable
> B-Tree for full scans and "count(*)" operations."
>
> Does it mean that performance of count(*) has been improved in 3.8.1
Yes.
> and if yes
Hi ,
I see that in release history for 3.8.1 below item.
"Estimate the sizes of table and index rows and use the smallest applicable
B-Tree for full scans and "count(*)" operations."
Does it mean that performance of count(*) has been improved in 3.8.1 and if yes
by how much? We were using
4 matches
Mail list logo