Class E202_PvtPrefilter

Assembly: redb.Examples.dll

Dumps SQL for the cases the PVT prefilter is meant to handle, so the same run can be
compared with and without the cutting step. See docs/PVT_PREFILTER_PLAN.md.
The prefilter is opt-in. Run twice and diff:
dotnet run --project redb.Examples -- E202 (off)
REDB_PVT_PREFILTER=1 dotnet run --project redb.Examples -- E202 (on)
Each case also executes, and the example compares the returned id sets between the two
runs by writing them to the dump. The prefilter is a superset by construction, so the id
sets MUST be identical. A difference is a defect, not a tuning question.
Expected shapes when enabled:
top-level OR -> disjunction spliced into the _values scan (Row form)
top-level AND -> Row form too, when the single branch covers the whole pivot
unanalysable -> no prefilter at all, SQL identical to the disabled run

[ExampleMeta("E202", "PVT prefilter: SQL with and without the cutting step", "Query", ExampleTier.Pro, 200, new string[] { "Sql", "Debug", "Prefilter", "Pro", "Pvt" }, RelatedApis = new string[] { "IRedbQueryable.ToSqlStringAsync" })]
public class E202_PvtPrefilter : ExampleBase

Inheritance

Object→ExampleBase→E202_PvtPrefilter

Inherited Members

Methods

RunAsync(IRedbService)

Run the example and return result.

public override Task<ExampleResult> RunAsync(IRedbService redb)