Re: [sqlite] virtual table xBestIndex and SQLITE_CONSTRAINT and zErrMsg

On 2/19/19, dave wrote: > I noticed that in 3.26 a feature was added whereby a proposed execution plan > can be rejected in vtables by returning SQLITE_CONSTRAINT. I welcome this > addition, but I have lost a capability relative to the prior scheme of using > high query cost along with a special

[sqlite] virtual table xBestIndex and SQLITE_CONSTRAINT and zErrMsg

I noticed that in 3.26 a feature was added whereby a proposed execution plan can be rejected in vtables by returning SQLITE_CONSTRAINT. I welcome this addition, but I have lost a capability relative to the prior scheme of using high query cost along with a special flag communicated in pIdxInfo->id