Re: [sqlite] Query Planner for Virtual Tables: link table evaluation & transitive property of constraints not used

Hello, I went forward and implemented the suggestion I made. It works quite nice, so I decided to share a patch (https://www.dropbox.com/sh/buim6b4hevg7db3/AAD75j1NkXSakx-1_iGu1QW4a?dl=0). Statement: I (the author of this code patch) dedicate any and all copyright interest in this code patch

Re: [sqlite] Query Planner for Virtual Tables: link table evaluation & transitive property of constraints not used

- 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

Re: [sqlite] Query Planner for Virtual Tables: link table evaluation & transitive property of constraints not used

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

Re: [sqlite] Query Planner for Virtual Tables: link table evaluation & transitive property of constraints not used

- 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

Re: [sqlite] Query Planner for Virtual Tables: link table evaluation & transitive property of constraints not used

I would concur in that SQLite is asking "which subset of the given constraints yields the most efficient access". The possible query plans are 1) A() -> B(ID) -> C(LINKID) 2) C() -> B(LINKID) -> A(ID) 3) B() -> A(ID) + C(LINKID) or B() -> C(LINKID) + A(ID) 4) A() -> C() -> B(ID,LINKID) or

Re: [sqlite] Query Planner for Virtual Tables: link table evaluation & transitive property of constraints not used

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

Re: [sqlite] Query Planner for Virtual Tables: link table evaluation & transitive property of constraints not used

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

[sqlite] Query Planner for Virtual Tables: link table evaluation & transitive property of constraints not used

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