Thanks for the report. The bug you found is probably harmless on most systems. But it is certainly worth fixing. http://www.sqlite.org/src/info/19fe4a0a475bd94
On Fri, Oct 17, 2014 at 5:11 PM, Peter Aronson <[email protected]> wrote: > No big deal, but on line 885 of shell.c, did you really mean to test if > azArg (of type char**) was greater than 0 rather than not equal to 0? It > throws a warning on Solaris 9 with the SUNPro compiler. > > > On Friday, October 17, 2014 10:00 AM, D. Richard Hipp <[email protected]> > wrote: > > > > > > > >SQLite version 3.8.7 is now available on the SQLite website: > > > > http://www.sqlite.org/ > > http://www.sqlite.org/download.html > > http://www.sqlite.org/releaselog/3_8_7.html > > > >SQLite version 3.8.7 is a regularly scheduled maintenance release. > Upgrading from all prior versions is recommended. > > > >Most of the changes from the previous release have been > micro-optimizations designed to help SQLite run a little faster. Each > individual optimization has an unmeasurably small performance impact. But > the improvements add up. Measured on a well-defined workload (which the > SQLite developers use as a proxy for a typical application workload) using > cachegrind on Linux and compiled with gcc 4.8.1 and -Os on x64 linux, the > current release does over 20% more work for the same number of CPU cycles > compared to the previous release. Cachegrind is not a real CPU, and the > workload used for measurement is only a proxy. So your performance may > vary. We expect to see about half the measured and reported improvement in > real-world applications. 10% is less than 20% but it is still pretty good, > we think. > > > >This release includes a new set of C-language interfaces that have > unsigned 64-bit instead of signed 32-bit length parameters. The new APIs do > not provide any new capabilities. But they do make it easier to write > applications that are more resistant to integer overflow vulnerabilities. > > > >This release also includes a new sorter that is able to use multiple > threads to help with large sort operations. (Sort operations are sometimes > required to implement ORDER BY and/or GROUP BY clauses and are almost > always required for CREATE INDEX.) The multi-threads sorter is turned off > by default and must be enabled using the "PRAGMA threads" SQL command. Note > that the multi-threaded sorter provides faster real-time performance for > large sorts, but it also uses more CPU cycles and more energy. > > > >As always, please report any problems to the [email protected] > mailing list or directly to me. Thanks > >-- > >D. Richard Hipp > >[email protected] > > > > > > > >_______________________________________________ > >sqlite-announce mailing list > >[email protected] > >http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-announce > > > > > > > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
