| Package | Description |
|---|---|
| gudusoft.gsqlparser.dlineage.dynamicsql |
| Modifier and Type | Method and Description |
|---|---|
DynamicSqlLineageResolver.MaterializedSite |
DynamicSqlLineageResolver.MaterializedSite.mergedWith(DynamicSqlLineageResolver.MaterializedSite other)
One variant standing for this one and
other, which gives the same text (two bindings with the same
result, Mantis 4962): the weaker evidence of the two, so no hole and no uncertainty is lost. |
DynamicSqlLineageResolver.MaterializedSite |
DynamicSqlLineageResolver.MaterializedSite.withNote(String note)
The same variant, its diagnostic carrying
note too (sources merged when variants coincide). |
| Modifier and Type | Method and Description |
|---|---|
static Map<TCustomSqlStatement,DynamicSqlLineageResolver.MaterializedSite> |
DynamicSqlLineageResolver.materializeSites(TCustomSqlStatement procAst,
EDbVendor vendor,
Map<String,SqlValue> bindings,
DynamicLineageOptions options)
Same as
DynamicSqlLineageResolver.materializeSitesWithoutBindings(gudusoft.gsqlparser.TCustomSqlStatement, gudusoft.gsqlparser.EDbVendor, gudusoft.gsqlparser.dlineage.dynamicsql.DynamicLineageOptions), but with caller-supplied parameter
bindings (e.g. |
static Map<TCustomSqlStatement,DynamicSqlLineageResolver.MaterializedSite> |
DynamicSqlLineageResolver.materializeSitesWithoutBindings(TCustomSqlStatement procAst,
EDbVendor vendor,
DynamicLineageOptions options)
Default-path hook for
DataFlowAnalyzer: abstractly evaluate a procedure's
dynamic-SQL string building with NO call-site bindings — only literal parameter
defaults are seeded — and return the materialized string per EXEC/sp_executesql
statement node (identity-keyed against the SAME parse tree that was passed in). |
static List<Map<TCustomSqlStatement,DynamicSqlLineageResolver.MaterializedSite>> |
DynamicSqlLineageResolver.materializeSiteVariants(TCustomSqlStatement procAst,
EDbVendor vendor,
Map<String,SqlValue> bindings,
DynamicLineageOptions options)
Materialize all bounded, row-correlated constant-relation variants for a
procedure.
|
static List<Map<TCustomSqlStatement,DynamicSqlLineageResolver.MaterializedSite>> |
DynamicSqlLineageResolver.materializeSiteVariants(TCustomSqlStatement procAst,
EDbVendor vendor,
Map<String,SqlValue> bindings,
DynamicLineageOptions options,
BindingSource source)
DynamicSqlLineageResolver.materializeSiteVariants(TCustomSqlStatement, EDbVendor, Map, DynamicLineageOptions), each site
stamped with where its bindings came from (Mantis 4962): a site's diagnostic names the binding, and the
default analysis publishes a site some binding reached with the bound variants only. |
| Modifier and Type | Method and Description |
|---|---|
static List<SqlFragment> |
DynamicSqlEdgeProof.holesOf(DynamicSqlLineageResolver.MaterializedSite site)
Hole diagnostics for a site, for the "which variable blocked what" report.
|
static List<int[]> |
DynamicSqlEdgeProof.holeSpansOf(DynamicSqlLineageResolver.MaterializedSite site)
Character spans
[start, end) of every non-literal fragment of site,
in fragment order — index-aligned with DynamicSqlEdgeProof.holesOf(gudusoft.gsqlparser.dlineage.dynamicsql.DynamicSqlLineageResolver.MaterializedSite). |
DynamicSqlLineageResolver.MaterializedSite |
DynamicSqlLineageResolver.MaterializedSite.mergedWith(DynamicSqlLineageResolver.MaterializedSite other)
One variant standing for this one and
other, which gives the same text (two bindings with the same
result, Mantis 4962): the weaker evidence of the two, so no hole and no uncertainty is lost. |
static DynamicSqlEdgeProof.Verdict |
DynamicSqlEdgeProof.prove(DynamicSqlLineageResolver.MaterializedSite site,
TCustomSqlStatement statement,
DynamicSqlEdgeProof.EdgeEvidence evidence,
BindingTraceRegistry traces,
EDbVendor vendor)
Prove one candidate edge against a materialized site.
|