To get answers in a similar situation I found useful the EXPLAIN QUERY PLAN command.
On Fri, May 24, 2013 at 3:56 PM, kyan <alfasud...@gmail.com> wrote: > On Fri, May 24, 2013 at 4:46 PM, Marc L. Allen > <mlal...@outsitenetworks.com>wrote: > >> It's exhaustive in that it absolutely verifies if the key exists or not. >> However, it doesn't necessarily do a full database scan. I assume it uses >> available indexes and does a standard lookup on the key. >> >> So, it still might be fast enough for what you want (though I missed the >> beginning of the thread). >> >> -----Original Message----- >> From: sqlite-users-boun...@sqlite.org [mailto: >> sqlite-users-boun...@sqlite.org] On Behalf Of Richard Hipp >> >> On Fri, May 24, 2013 at 7:07 AM, kyan <alfasud...@gmail.com> wrote: >> >> It is exhaustive >> > > Thank you both for your answers. > > Since I am writing code for an application server that connects to > databases of different database vendors used by other development teams I > have no way of knowing anything about the underlying database, so I will > not take any chances. > > -- > Constantine Yannakopoulos > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
