Class PvtPrefilterRenderer
Renders a into the SQL fragment that goes into the WHERE of the
_values scan feeding the pivot aggregate. See docs/PVT_PREFILTER_PLAN.md.
The analysis is provider-agnostic and lives in . This part is
not: PostgreSQL concatenates with "||" and has ILIKE, MSSql concatenates with "+" and needs an
explicit COLLATE, SQLite has neither ILIKE nor a case-sensitive LIKE. Each provider therefore
keeps its own renderer next to the operator mapping it already owns in ProSqlBuilder.
public static class PvtPrefilterRenderer
Inheritance
Methods
RenderBranch(string, PvtPrefilterBranch, SqlParameterCollector, ISqlDialect)
Renders one branch: the structure it belongs to, then every predicate on it.
public static string RenderBranch(string alias, PvtPrefilterBranch branch, SqlParameterCollector collector, ISqlDialect dialect)
RenderRowFilter(PvtPrefilterPlan, string, SqlParameterCollector, ISqlDialect)
Branches are ORed: a _values row belongs to exactly one structure, so a disjunction is the
public static string RenderRowFilter(PvtPrefilterPlan plan, string valuesAlias, SqlParameterCollector collector, ISqlDialect dialect)