On Fri, Sep 14, 2012 at 5:24 PM, Roger Binns <rog...@rogerbinns.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > >> Is there a chance that the change will go into SQLite mainline? > > > > Not without a copyright release. > > And it may require more especially if you are an employee. See the bottom > section of http://www.sqlite.org/copyright.html > > And of course it is more than the few lines of changes - all the test > suites have to be updated to ensure no breakage and 100% coverage. > Furthermore, the change is incomplete. With the patch shown, EXPLAIN QUERY PLAN gives an incorrect explanation of what is happening. And sqlite3_stmt_status(pStmt, SQLITE_STMTSTATUS_FULLSCAN_STEP, ...) does not count the full-scan steps that occur as part of a covering-index scan. There may be other issues; these are just the ones I have found so far. > > Roger > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iEYEARECAAYFAlBToHQACgkQmOOfHg372QR1XgCfZvoXr2uKaVFFDo46sEQZiML6 > X3UAn0qWun5ldvSJdGj4SEN/n7dVBd7V > =GQzU > -----END PGP SIGNATURE----- > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
