On Mon, Mar 9, 2009 at 12:08 AM, Igor Tandetnik wrote:
>
> It can't. "hash" column is not part of the index.
>
Right... I should have seen that.
> > Would re-ordering our unique index to be (name, id, value, ...)
> > rather than (name, value, id, ...) allow a query with only name and
> > id to
On Sun, Mar 8, 2009 at 9:46 PM, Igor Tandetnik wrote:
> When all columns in the SELECT come from the index, SQLite can get all
> their values directly from the index and avoid reading actual table. So
> it saves an index-to-table lookup.
>
Thanks, that helps.
> Note also that, as far as SQLit
It seems like sqlite (3.6.6.2) chooses different indexes depending on which
columns are selected for *output* and I wonder whether this is a bug?
In some cases monotone experiences poor performance because of this
behaviour (which we can easily work around) but I thought I'd check and see
if this
3 matches
Mail list logo