[sqlite] eponymous vtables, xBestIndex, and required parameters...

2017-10-04 Thread dave
Folks; I am building a system which uses the virtual tables facilityto join some non-relational data (coming from system APIs) to relational data. I am using the virtual table mechanism in sqlite, and in particular am creating 'eponymous' virtual tables to create 'table valued functions'. I ha

Re: [sqlite] eponymous vtables, xBestIndex, and required parameters...

2017-10-04 Thread Richard Hipp
On 10/4/17, dave wrote: > 1) is there an orthodox method of indicating that a query plan request from > xBestIndex is a no-go, Give that plan a huge estimatedCost. As a backup, in the exceedingly unlikely event that SQLite chooses your no-go plan in spite of the huge estimatedCost, also provide

Re: [sqlite] eponymous vtables, xBestIndex, and required parameters...

2017-10-05 Thread dave
> ... > > 1) is there an orthodox method of indicating that a query > plan request from > > xBestIndex is a no-go, > > Give that plan a huge estimatedCost. > > As a backup, in the exceedingly unlikely event that SQLite chooses > your no-go plan in spite of the huge estimatedCost, also provide a

Re: [sqlite] eponymous vtables, xBestIndex, and required parameters...

2017-10-05 Thread Richard Hipp
On 10/5/17, dave wrote: > > I suppose the converse is true, that the extimated cost > relative to OTHER virtual/physical tables does NOT matter. > It matters some, but it is of lesser importance. -- D. Richard Hipp d...@sqlite.org ___ sqlite-users mail