docs(sql): p_-prefixed Oracle examples in the four stale doc comments (final-review nit)

2026-08-05 07:28:24 -04:00
parent db295c1439
commit bfdf74ec0b
4 changed files with 9 additions and 9 deletions
@@ -18,7 +18,7 @@ namespace ZB.MOM.WW.OtOpcUa.Driver.Sql;
 ///     the allow-list cannot itself be an injection vector. No identifier is quoted into text on this path.
 ///     The bind names come from <see cref="ISqlDialect.ParameterBindName"/> over those two base names, so
 ///     they can never disagree with the markers in the dialect's own catalog SQL (<c>@schema</c> on SQL
-///     Server, <c>:schema</c> on Oracle).</para>
+///     Server, <c>:p_schema</c> on Oracle).</para>
 ///     <para><b>Failures throw; they do not degrade to an empty catalog.</b> An empty catalog would reject
 ///     every tag, which is indistinguishable at the OPC UA surface from a database whose objects were all
 ///     dropped. A caller that cannot read the catalog has not learned that the tags are invalid — it has
@@ -14,13 +14,13 @@ namespace ZB.MOM.WW.OtOpcUa.Driver.Sql;
 ///     <para><b>Injection boundary (design §8.1).</b> Identifiers reach the command text through
 ///     <see cref="ISqlDialect.QuoteIdentifier"/> and nothing else; every authored value becomes a
 ///     <c>k0</c>/<c>w</c> parameter — spelled with the dialect's own <see cref="ISqlDialect.ParameterMarker"/>
-///     (<c>@k0</c> on SQL Server, <c>:k0</c> on Oracle) — with the value carried in
+///     (<c>@k0</c> on SQL Server, <c>:p_k0</c> on Oracle) — with the value carried in
 ///     <see cref="SqlQueryPlan.Parameters"/>. There is no interpolation of tag content into SQL anywhere in
 ///     this type.</para>
 ///     <para><b>The base names are this planner's, the spelling is the dialect's.</b> Each plan carries the
 ///     markers it emitted <em>and</em> the matching <see cref="ISqlDialect.ParameterBindName"/>s, so the
 ///     reader binds what the planner minted instead of re-deriving a provider convention — the two differ on
-///     ODP.NET (<c>:k0</c> in the text, bare <c>k0</c> on the parameter).</para>
+///     ODP.NET (<c>:p_k0</c> in the text, bare <c>p_k0</c> on the parameter).</para>
 /// </summary>
 public static class SqlGroupPlanner
 {
@@ -12,8 +12,8 @@ namespace ZB.MOM.WW.OtOpcUa.Driver.Sql;
 ///     <see cref="DbParameter"/> named by the positionally-aligned <see cref="ParameterBindNames"/>. There is
 ///     no path by which a tag's <c>keyValue</c> or <c>whereValue</c> reaches the command text.</para>
 ///     <para><b>Markers and bind names are carried separately</b> because they are not the same string on
-///     every provider: ODP.NET's text says <c>:k0</c> while its <see cref="DbParameter.ParameterName"/> is the
-///     bare <c>k0</c>. Both lists are positionally aligned with <see cref="Parameters"/>, so a binding site
+///     every provider: ODP.NET's text says <c>:p_k0</c> while its <see cref="DbParameter.ParameterName"/> is the
+///     bare <c>p_k0</c>. Both lists are positionally aligned with <see cref="Parameters"/>, so a binding site
 ///     copies the pairing the planner minted rather than re-deriving a provider convention it does not own.</para>
 ///     <para>Produced only by <see cref="SqlGroupPlanner.Plan"/>; consumed by the poll reader, which executes
 ///     <see cref="SqlText"/> once and slices the rows back to per-member snapshots.</para>