Sorry for the ambiguity - yes, I believe that's the case. It's certainly the case with every other database I've used, and given what I know of SQLite I can't see any reason why it wouldn't (though I will say that I yet haven't delved too far into how joins are processed, so I could be completely wrong). EXPLAINing some simple test queries containing joins both with and without indexes on the tables show different execution plans; I won't claim to have thoroughly dissected the plans, but it's certainly doing something different when the indexes are/are not present, which I think is a good sign.
-Tom > -----Original Message----- > From: Ted Unangst [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 19, 2005 1:28 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Indexing problem > > Thomas Briggs wrote: > > > I think the common misconception is that indexes on multiple > > individual columns can be used in conjunction with one > another, which > > isn't the case (unless you're talking about bitmap indexes, > but since > > SQLite doesn't have those, we clearly aren't :P). Once you get > > comfortable with the fact that only a single index can be used > > everything makes sense. > > Just to be clear, you mean a single index per table, right? > Two tables > in a where can use two indices in sqlite? > > > -- > Ted Unangst www.coverity.com Coverity, Inc. >
