- Original Message -
From: "Josef Kucera"
To: "General Discussion of SQLite Database"
Sent: Monday, December 15, 2014 5:37 PM
Subject: Re: [sqlite] Query Planner for Virtual Tables: link table
evaluation & transitive property of constraints not used
- Orig
- Original Message -
From: "Nico Williams"
To: "General Discussion of SQLite Database"
Sent: Monday, December 15, 2014 5:16 PM
Subject: Re: [sqlite] Query Planner for Virtual Tables: link table
evaluation & transitive property of constraints not used
On Mo
On Mon, Dec 15, 2014 at 06:23:31PM +0700, Dan Kennedy wrote:
> It's tricky. As you say, xBestIndex() will currently be invoked
> twice - once with no constraints usable and once with both "b.id=?"
> and "b.linkid=?" usable. I guess the reason it is not invoked in the
> other ways you suggest is tha
- Original Message -
From: "Hick Gunter"
To: "'General Discussion of SQLite Database'"
Sent: Monday, December 15, 2014 2:40 PM
Subject: Re: [sqlite] Query Planner for Virtual Tables: link table
evaluation & transitive property of constraints not use
re? Plan 3 is better only for very sparse link
tables where b < a < c is true.
-Ursprüngliche Nachricht-
Von: Dan Kennedy [mailto:danielk1...@gmail.com]
Gesendet: Montag, 15. Dezember 2014 12:24
An: General Discussion of SQLite Database
Betreff: Re: [sqlite] Query Planner for
On 12/15/2014 13:23 PM, Dan Kennedy wrote:
> On 12/12/2014 09:22 PM, Josef Kučera wrote:
> > Hello,
> > I am trying to use SQLite's marvellous Virtual Table mechanism as a SQL
> > layer for querying an in memory storage. This works good, but I have a
> > problem with more complex queries. When quer
On 12/12/2014 09:22 PM, Josef Kučera wrote:
Hello,
I am trying to use SQLite's marvellous Virtual Table mechanism as a SQL
layer for querying an in memory storage. This works good, but I have a
problem with more complex queries. When querying a real SQLite database it
correctly moves the constant
Hello,
I am trying to use SQLite's marvellous Virtual Table mechanism as a SQL
layer for querying an in memory storage. This works good, but I have a
problem with more complex queries. When querying a real SQLite database it
correctly moves the constant conditions across joined tables to optimize
t
8 matches
Mail list logo