On 04/08/2010, at 11:12 PM, Igor Tandetnik wrote: > I believe the two are equivalent. SQLite essentially rewrites IN to EXISTS - > it certainly doesn't generate the complete resultset from the nested select > and then go searching inside that. > > I noticed anecdotally that SQLite may optimize complex statements involving > IN better than those involving EXISTS, but I don't have formal evidence.
That's good to know. Thanks Igor. I wasn't aware that "in" prevents a full table scan in the same way (or better) than EXISTS does. Thanks, Tom BareFeetWare -- Comparison of SQLite GUI tools: http://www.barefeetware.com/sqlite/compare/?ml _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
