Thanks... that certainly clarifies it. Also, thanks to Dan who responded similarly.
-----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Richard Hipp Sent: Thursday, August 29, 2013 11:58 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] segmentation fault with 3.8.0 On Thu, Aug 29, 2013 at 11:47 AM, Marc L. Allen <mlal...@outsitenetworks.com > wrote: > Silly question.. I looked at the fix. Why ignore indexes with greater > than 4 fields? Isn't that a bit risky? Wouldn't it be better to > ignore the fields after the 4th one for planning? > The whereShortCut() routine is merely an optimization. It provides a quick plan for the common case of a single-table query using an equality constraint on a PRIMARY KEY or UNIQUE index. Anything that falls through whereShortCut() goes into the regular query planner and will get analyzed thoroughly there. You could omit the whereShortCut() routine entirely and SQLite would still give the correct answer. The only downside is that sqlite3_prepare_v2() would run slightly slower in the common case. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users This email and any attachments are only for use by the intended recipient(s) and may contain legally privileged, confidential, proprietary or otherwise private information. Any unauthorized use, reproduction, dissemination, distribution or other disclosure of the contents of this e-mail or its attachments is strictly prohibited. If you have received this email in error, please notify the sender immediately and delete the original. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
