Skip to content

fix(syntax): give numeric Snowflake operands a wrong-kind case and verify 74 more forms - #222

Merged
kvlonge merged 12 commits into
mainfrom
feat/syntax-pool-23
Nov 13, 2026
Merged

kvlonge merged 12 commits into
mainfrom
feat/syntax-pool-23

Conversation

@kvlonge

@kvlonge kvlonge commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

Why

Numeric Snowflake operands had no wrong-kind case, so reviewers rejected forms that otherwise held, and some recorded verdicts disagreed with the parser.

Changes

  • Numeric operands (<integer>, <rows>, <num> and similar) get the integer class and a "string in place of a number" case. Name operands are unchanged.
  • Parser verdicts match the receipts for SHOW, task, routine, listing, Iceberg, Openflow, interactive warehouse and partial CREATE shapes. SHOW DELEGATED AUTHORIZATIONS keeps BY USER and TO SECURITY INTEGRATION as its scope.
  • 27 security_admin negatives the docs also accept are suppressed with reasons. Two receipt batches are pinned, and 74 unobservable records that now have receipts are removed.

Verification

  • Verified forms: 2,709 to 2,730 of 3,351. Gross +74, drops 53, net +21.
  • Drops: 41 forms failed fresh review on gaps the current criteria catch (missing cases for function arguments, empty names, raw-string type parameters, docs added GRAPH_RUN_GROUP_ID). 12 have a new numeric case the capture guard holds or the importer refuses (errno 90106). The list is in a comment below.
  • Fresh reviewers, not the author: 103 approved, 43 rejected. Four approvals were withdrawn where another reviewer rejected the same gap. Earlier rejections for name operands stand.
  • Caveat: 655 verified forms (442 function forms) still have a name operand with no wrong-kind case. The next change classifies them and re-baselines.
  • 10 approvals I spot-checked against the docs, the receipts and their numeric case (all SHOW forms: ICEBERG TABLES, NOTEBOOKS, GRANTS IN DCM PROJECT, USERS, DEPLOYMENTS, APPLICATION ROLES, artifact repository FILES, DATABASE ROLES, CORTEX BASE MODELS, EXTERNAL TABLES) are linked in the comment.
  • One code review and one dropped-list review; findings fixed. make check-ci passes on the final head.

…d routine modifiers in the tree

Parse the Snowflake forms whose recorded verdicts the parser missed:
SHOW containers and lone kind words, new SHOW kinds (VOLUMES,
DELEGATED AUTHORIZATIONS), DESC and DROP of lone kinds, structured
ALTER OPENFLOW, DEPLOYMENT and ROLE, CREATE TASK without properties,
table stages after a dot in PUT, and refusals for EXECUTE of a
non-kind, CAST to PRECISION, quoted session variables, SET without a
variable name and CREATE INDEX on a reserved word.

Keep ROOT ONLY, OR ALTER, SECURE, EXTERNAL and TEMPORARY as fields
instead of folding them into the kind or dropping them.
…lake docs already allow

Remove 27 wrong-outcome obligations whose case either relies on a
documented remainder or cannot express an integration type list, each
with a docs reason in limits.toml.
…OT POLICY before SET as a snapshot name

A single SET or UNSET CONTACT on a table kept the shared ALTER TABLE
tree with a raw action; it now keeps the governance tree with the
purpose and the contact name. ALTER SNAPSHOT POLICY SET COMMENT names
a snapshot called POLICY, as Snowflake reads it, and the nameless
SNAPSHOT POLICY SET TAG and UNSET forms are refused.
…outine maps, Iceberg versions and partial CREATE kinds

SHOW AVAILABLE LISTINGS keeps its IS_IMPORTED, IS_ORGANIZATION and
IS_SHARED_WITH_ME filters. External function HEADERS take bare words
and COMPRESSION and the translators take strings. AT reads Iceberg
VERSION_TAG and VERSION_REF. A volatile file format keeps VOLATILE.
A named argument refuses an unquoted stage, CREATE refuses METRIC
alone and an IF after the kind that does not start IF NOT EXISTS.
…wflake forms

Each form was read against its documentation page, obligations, cases
and parse trees by a reviewer other than the parser's author, and is
bound to its fingerprint and definition. 36 reviewed forms were
rejected and stay unverified.
Operands the pages name <rows>, <integer>, <*_num>, <*_seconds>, <length>,
<precision> or <scale> were read as plain operands, so they had no string
literal negative while every name and string operand had one. They now take
the integer class: a positive with an integer and a negative with a string
literal in its place. The recorded docs/engine conflicts on SKIP_HEADER,
MAX_STALENESS and SHOW ... LIMIT keep their suppressions under the new
class note.
BY USER, BY and TO SECURITY INTEGRATION were folded into the object kind and
the name went to the FOR target. The kind is now DELEGATED AUTHORIZATIONS, the
clause is the scope kind and the user or integration is the scope, with its
quoting.
…s for the batch 23 receipts

Fresh reviewers re-read SHOW RUN METRICS and PARAMETERS IN EXPERIMENT
against the wrong-kind criterion after their numeric operands gained
obligations. Marks and arity follow the cases regenerated with the new
obligations and the batch 23 receipts; the evidence pin follows.
…iven a string

Snowflake refuses a string as SEQUENCE_NUMBER, as a data metric
function's GROUP LIMIT and as a SHOW row count, so the parser now does
too. It parses a string as a routine's MAX_BATCH_ROWS,
MAX_BATCH_RETRIES or BATCH_TIMEOUT_SECS, and a semantic view's
MAX_STALENESS, which the parser now reads and keeps as a property.

ALTER SNAPSHOT POLICY SET reads POLICY as a snapshot name only before
COMMENT, the one recorded case; any other SET stays a snapshot policy
with its name left out. Tests now also check the scope name of a lone
BY USER, the kind of SHOW TASKS with ROOT ONLY, and the routine
modifiers kept as fields.
…iven a string

Pin the evidence with the receipts for the wrong-kind cases of numeric
operands, the remaining SHOW, ALTER and CREATE shapes and the DCM
definitions, and refresh the marks they settle.

Give the two new SHOW MULTI PARTY APPROVAL POLICIES LIMIT obligations
fresh ids instead of the two that the suppressed IN negatives retired,
so ids keep their meaning, and point three unobservable records at the
integer obligations that replaced theirs.
… MAX_STALENESS as a string

Snowflake refuses CREATE INTERACTIVE WAREHOUSE with no name, with IF
EXISTS, or with a bare parenthesised list after the name, so the opaque
check now knows the kind and refuses them too. A semantic view's
MAX_STALENESS takes a string: Snowflake refuses a number there and
parses a string, so the parser does the same.
…owflake forms

Fresh reviewers read 146 review-only forms in full and approved 107.
Four approvals are withdrawn because another reviewer rejected the same
gap elsewhere: a missing case for a required function argument, and a
repeated list item with no missing case. The other rejections stand
until their gaps are fixed.

Re-record the baseline. Against the previous one, 74 forms are gained
and 53 lost: 41 previously verified forms failed review on gaps the
current criteria catch, and 12 forms have a new numeric case that the
capture guard holds or whose receipt the importer refuses. Remove the
74 unobservable records whose cases now have receipts and the
disagreements the parser now agrees with.

kvlonge commented Nov 13, 2026

Copy link
Copy Markdown
Contributor Author

Dropped and loosened obligations, re-baseline drops and review details

1. 27 security_admin derived obligations suppressed with docs reasons (0b426da)

Each was a derived rejection whose SQL the docs also accept, or a class that does not apply. Case changes: 19 evidence cases removed with them.

  • alter-account-set-ingress-policy.unset-ingress-policy negative_neighbour the form without its required INGRESS: ALTER ACCOUNT UNSET <param_name> [ , ... ] is documented on the ALTER ACCOUNT page, so ALTER ACCOUNT UNSET POLICY unsets a parameter named POLICY (https://docs.snowflake.com/en/sql-reference/sql/alter
  • alter-account.unset-authentication-session-policy negative_neighbour the form without its required { AUTHENTICATION | SESSION }: ALTER ACCOUNT UNSET <param_name> [ , ... ] is documented on the ALTER ACCOUNT page, so ALTER ACCOUNT UNSET POLICY unsets a parameter named POLICY (https://docs.snowflake.com/en/sql-reference/sql/alter
  • alter-account.unset-packages-password-multi negative_neighbour the form without its required { PACKAGES | PASSWORD | MULTI PARTY APPROVAL }: ALTER ACCOUNT UNSET <param_name> [ , ... ] is documented on the ALTER ACCOUNT page, so ALTER ACCOUNT UNSET POLICY unsets a parameter named POLICY (https://docs.snowflake.com/en/sql-reference/sql/alter
  • alter-organization-user.set negative_neighbour the form without its required ORGANIZATION: without ORGANIZATION the remainder is ALTER USER SET COMMENT = '', documented on the ALTER USER page (https://docs.snowflake.com/en/sql-reference/sql/alter-user)
  • alter-user.unset-authentication-password-session negative_neighbour the form without its required { AUTHENTICATION | PASSWORD | SESSION }: ALTER USER [ IF EXISTS ] [ ] UNSET { <object_property_name> | <object_param_name> | <session_param_name> } [ , ... ] is documented with the name optional, so the remainder unsets a property of
  • alter-user.unset-authentication-password-session negative_neighbour the form without its required POLICY: ALTER USER [ IF EXISTS ] [ ] UNSET { <object_property_name> | <object_param_name> | <session_param_name> } [ , ... ] is documented with the name optional, so the remainder unsets a property of
  • alter-user.unset-tag required_operand_missing <tag_name>: ALTER USER [ IF EXISTS ] [ ] UNSET { <object_property_name> | <object_param_name> | <session_param_name> } [ , ... ] is documented with the name optional, so the remainder unsets a property of
  • create-database-role.define-database-role required_operand_missing : DEFINE DATABASE ROLE ; is DEFINE DATABASE with the database named ROLE; DEFINE DATABASE takes the CREATE OR ALTER DATABASE syntax (https://docs.snowflake.com/en/sql-reference/sql/create-databas
  • create-failover-group.object-types-allowed-accounts identifier_class <integration_type_name>: <integration_type_name> is a documented keyword list (SECURITY INTEGRATIONS, API INTEGRATIONS, ...), not an identifier, so identifier-class cases do not apply (https://docs.snowflake.com/en/sql-refere
  • create-failover-group.object-types-allowed-accounts identifier_class <integration_type_name>: <integration_type_name> is a documented keyword list (SECURITY INTEGRATIONS, API INTEGRATIONS, ...), not an identifier, so identifier-class cases do not apply (https://docs.snowflake.com/en/sql-refere
  • create-replication-group.object-types-allowed-accounts identifier_class <integration_type_name>: <integration_type_name> is a documented keyword list (SECURITY INTEGRATIONS, API INTEGRATIONS, ...), not an identifier, so identifier-class cases do not apply (https://docs.snowflake.com/en/sql-refere
  • create-replication-group.object-types-allowed-accounts identifier_class <integration_type_name>: <integration_type_name> is a documented keyword list (SECURITY INTEGRATIONS, API INTEGRATIONS, ...), not an identifier, so identifier-class cases do not apply (https://docs.snowflake.com/en/sql-refere
  • grant-privilege.create-schema-modify-monitor negative_neighbour the form without its required DATABASE after TO: without DATABASE after TO the remainder is { accountObjectPrivileges } ON DATABASE <object_name> TO [ ROLE ] <role_name>, the documented account-role grant on the same page (https://docs.snowflake.com
  • revoke-privilege.create-schema-modify-monitor negative_neighbour the form without its required DATABASE after FROM: without DATABASE after FROM the remainder is { accountObjectPrivileges } ON DATABASE <object_name> FROM [ ROLE ] <role_name>, the documented account-role revoke on the same page (https://docs.snowflak
  • show-authentication-policies negative_neighbour the form without its required DATABASE after IN in [ IN { ACCOUNT | DATABASE | DATABASE <database_name> | SCHEMA | SCHEMA <schema_name> | APPLICATION <application_name> |…: SCHEMA is optional if a database is in use or if you specify the fully qualified schema_name (Parameters), so IN is the documented IN [ SCHEMA ] <schema_name> (https://docs.snowflake.com/en/sql
  • show-authentication-policies negative_neighbour the form without its required SCHEMA after IN in [ IN { ACCOUNT | DATABASE | DATABASE <database_name> | SCHEMA | SCHEMA <schema_name> | APPLICATION <application_name> |…: SCHEMA is optional if a database is in use or if you specify the fully qualified schema_name (Parameters), so IN is the documented IN [ SCHEMA ] <schema_name> (https://docs.snowflake.com/en/sql
  • show-authentication-policies negative_neighbour the form without its required APPLICATION after IN in [ IN { ACCOUNT | DATABASE | DATABASE <database_name> | SCHEMA | SCHEMA <schema_name> | APPLICATION <application_name> |…: SCHEMA is optional if a database is in use or if you specify the fully qualified schema_name (Parameters), so IN is the documented IN [ SCHEMA ] <schema_name> (https://docs.snowflake.com/en/sql
  • show-ingress-policies negative_neighbour the form without its required DATABASE after IN in [ IN { ACCOUNT | DATABASE | DATABASE <database_name> | SCHEMA | SCHEMA <schema_name> } | ON { ACCOUNT | USER…: SCHEMA is optional if a database is in use or if you specify the fully qualified schema_name (Parameters), so IN is the documented IN [ SCHEMA ] <schema_name> (https://docs.snowflake.com/en/sql
  • show-ingress-policies negative_neighbour the form without its required SCHEMA after IN in [ IN { ACCOUNT | DATABASE | DATABASE <database_name> | SCHEMA | SCHEMA <schema_name> } | ON { ACCOUNT | USER…: SCHEMA is optional if a database is in use or if you specify the fully qualified schema_name (Parameters), so IN is the documented IN [ SCHEMA ] <schema_name> (https://docs.snowflake.com/en/sql
  • show-multi-party-approval-policies.policies negative_neighbour the form without its required DATABASE after IN in [ IN { ACCOUNT | DATABASE | DATABASE <database_name> | SCHEMA | SCHEMA <schema_name> } ]: SCHEMA is optional if a database is in use or if you specify the fully qualified schema_name (Parameters), so IN is the documented IN [ SCHEMA ] <schema_name> (https://docs.snowflake.com/en/sql
  • show-multi-party-approval-policies.policies negative_neighbour the form without its required SCHEMA after IN in [ IN { ACCOUNT | DATABASE | DATABASE <database_name> | SCHEMA | SCHEMA <schema_name> } ]: SCHEMA is optional if a database is in use or if you specify the fully qualified schema_name (Parameters), so IN is the documented IN [ SCHEMA ] <schema_name> (https://docs.snowflake.com/en/sql
  • show-password-policies negative_neighbour the form without its required DATABASE after IN in [ IN { ACCOUNT | DATABASE | DATABASE <database_name> | SCHEMA | SCHEMA <schema_name> | APPLICATION <application_name> |…: SCHEMA is optional if a database is in use or if you specify the fully qualified schema_name (Parameters), so IN is the documented IN [ SCHEMA ] <schema_name> (https://docs.snowflake.com/en/sql
  • show-password-policies negative_neighbour the form without its required SCHEMA after IN in [ IN { ACCOUNT | DATABASE | DATABASE <database_name> | SCHEMA | SCHEMA <schema_name> | APPLICATION <application_name> |…: SCHEMA is optional if a database is in use or if you specify the fully qualified schema_name (Parameters), so IN is the documented IN [ SCHEMA ] <schema_name> (https://docs.snowflake.com/en/sql
  • show-password-policies negative_neighbour the form without its required APPLICATION after IN in [ IN { ACCOUNT | DATABASE | DATABASE <database_name> | SCHEMA | SCHEMA <schema_name> | APPLICATION <application_name> |…: SCHEMA is optional if a database is in use or if you specify the fully qualified schema_name (Parameters), so IN is the documented IN [ SCHEMA ] <schema_name> (https://docs.snowflake.com/en/sql
  • show-session-policies negative_neighbour the form without its required DATABASE after IN in [ IN { ACCOUNT | DATABASE | DATABASE <database_name> | SCHEMA | SCHEMA <schema_name> | APPLICATION <application_name> |…: SCHEMA is optional if a database is in use or if you specify the fully qualified schema_name (Parameters), so IN is the documented IN [ SCHEMA ] <schema_name> (https://docs.snowflake.com/en/sql
  • show-session-policies negative_neighbour the form without its required SCHEMA after IN in [ IN { ACCOUNT | DATABASE | DATABASE <database_name> | SCHEMA | SCHEMA <schema_name> | APPLICATION <application_name> |…: SCHEMA is optional if a database is in use or if you specify the fully qualified schema_name (Parameters), so IN is the documented IN [ SCHEMA ] <schema_name> (https://docs.snowflake.com/en/sql
  • show-session-policies negative_neighbour the form without its required APPLICATION after IN in [ IN { ACCOUNT | DATABASE | DATABASE <database_name> | SCHEMA | SCHEMA <schema_name> | APPLICATION <application_name> |…: SCHEMA is optional if a database is in use or if you specify the fully qualified schema_name (Parameters), so IN is the documented IN [ SCHEMA ] <schema_name> (https://docs.snowflake.com/en/sql

2. Numeric operand class (4fc6564)

  • 366 operand_type_class positives (360 'a valid operand', 5 'a valid expression', 1 'a valid identifier') are replaced, target for target, by 366 'a valid integer_literal' positives; 322 'a string literal in place of ' negatives are added. Nothing is loosened: every replaced positive still has a positive at the same target.
  • functions: 49 new integer negatives on ordinary call arguments are withdrawn by the existing class rule (count 43 to 92), because a call argument is an expression; no earlier obligation is affected.
  • 6 recorded docs/engine conflict suppressions move to the new note, unchanged reasons: SKIP_HEADER (DEFINE FILE FORMAT), MAX_STALENESS (3 semantic view forms), LIMIT ... FROM (SHOW OPENFLOW DATA PLANE INTEGRATIONS, SHOW ROW ACCESS POLICIES).

3. Other changes found by the independent review (none loosens an obligation)

  • Two ids would have been reused: suppressing the two IN negatives of SHOW MULTI PARTY APPROVAL POLICIES freed o041/o042, and the numeric class then reissued them for the LIMIT positive and negative. They are renumbered o043/o044, so retired ids keep their meaning.
  • 17 ddl negative-obligation cases moved from observe to settled accept on their batch 23 receipts (create-data-metric-function define o039; create-interactive-warehouse o030, o079, o092, o097, o102, o109, o114, o119, o130, o131; create-procedure define o118, o229, o404, o512; create-stage define o027, o950). Observe to accept by receipt, not reject to accept.
  • Three unobservable records now point at the integer obligations that replaced theirs (create-openflow-runtime o028→o080, o030→o082; drop-account o008→o020).

4. Re-baseline drops not recovered by review (12 forms)

  • 10 forms whose new numeric wrong-kind case is held by the capture guard (ALTER APPLICATION PACKAGE release channel/directive PATCH ×8, ALTER APPLICATION UPGRADE USING VERSION PATCH, CREATE API INTEGRATION external MCP). Guard-refused cases stay unverified.
  • 2 forms (SYSTEM$WAIT_FOR_STABLE_OPENFLOW_CONNECTORS/RUNTIMES) whose receipts the importer refused: errno 90106 has no established phase.

5. Previously verified forms that failed fresh review (41)

  • sf.ddl.alter-function-spcs.set-batch-timeout-secs: (b) <arg_data_type> in '( [ <arg_data_type> , ... ] )' never gets a wrong-kind case: only o007 '( INT , INT )' and o008 '( )'; no case like '( 'INT' )' or '( 1 )'. Grammar, outcomes and trees are otherwise fine.
  • sf.ddl.alter-function-spcs.set-max-batch-retries: (b) <arg_data_type> in '( [ <arg_data_type> , ... ] )' never gets a wrong-kind case: only o007 '( INT , INT )' and o008 '( )'; no case like '( 'INT' )' or '( 1 )'. Grammar, outcomes and trees are otherwise fine.
  • sf.ddl.alter-function.set-max-batch-rows: (b) <arg_data_type> in '( [ <arg_data_type> , ... ] )' never gets a wrong-kind case: only o007 '( INT , INT )' and o008 '( )'; no case like '( 'INT' )' or '( 1 )'. Grammar matches the External functions / Any language handler bloc
  • sf.ddl.create-stage.create-or-alter-stage.create-or-alter-stage: (b) The required URL operand ('://[//]' and its gcs/azure/s3compat forms) has no missing case (URL = ;) and no wrong-kind case (URL = m1). Only the keyword is dropped, e.g. 'CREATE OR ALTER STAGE v1 = 's3:/
  • sf.expressions.data-types-datetime.timestamp-variations: (d) Precision is not its own field: o011 and o031 'TIMESTAMP_LTZ ( 9 )' give data_type custom with name "TIMESTAMPLTZ(9)", and o020 gives "TIMESTAMPLTZ(0)", so the parameter is folded into a raw string. TIME and TIMESTAMP parse it
  • sf.expressions.data-types-numeric.number: (d) Precision and scale end up in a raw string: o002, o006 and o017 'NUMBER ( 9 , 2 )' give data_type custom with name "NUMBER(9, 2)", and o007 gives "NUMBER(9)", so they are not their own fields (DECIMAL gives precision:9, scale:
  • sf.functions.as-decimal-number.as-decimal: (b) No case omits the required <variant_expr> (no obligation for it; o002 is absent from the dossier and nothing like 'AS_DECIMAL ( )' exists). Only the optional precision and scale have missing cases (o006, o010).
  • sf.functions.as-decimal-number.as-number: (b) No case omits the required <variant_expr> (no obligation for it; o002 is absent from the dossier and nothing like 'AS_NUMBER ( )' exists). Only the optional precision and scale have missing cases (o006, o010).
  • sf.functions.complete-task-graphs: (a) The grammar leaves out the docs argument '[, GRAPH_RUN_GROUP_ID => '' ]'. The docs Syntax block ends with it after ERROR_ONLY; the grammar stops at ERROR_ONLY, and no obligation or case covers GRAPH_RUN_GROUP_ID.
  • sf.functions.current-task-graphs: (a) The grammar leaves out the docs argument '[, GRAPH_RUN_GROUP_ID => '' ]'. The docs Syntax block ends with it after GRAPH_NAME; the grammar stops at GRAPH_NAME, and no obligation or case covers it.
  • sf.functions.evaluate-candidate-network-policy: (d) o022 'SELECT SNOWFLAKE . . EVALUATE_CANDIDATE_NETWORK_POLICY (...)' is accepted (receipt semantic_error), but its tree invents an empty name: column {"name":"","quoted":false} with table SNOWFLAKE, where the schema was left ou
  • sf.functions.get-job-history: (d) o019 'SNOWFLAKE . . GET_JOB_HISTORY ( )' is accepted (receipt semantic_error) but the tree invents an empty schema name: column {"name":""} table SNOWFLAKE. Grammar 'RESULT_LIMIT = ' copies the docs quirk; cases use '
  • sf.functions.recommend-network-policy: (d) o015 'SELECT SNOWFLAKE . . RECOMMEND_NETWORK_POLICY ( LOOKBACK_DAYS => v1 )' is accepted (receipt semantic_error) but the tree invents an empty schema name: column {"name":""} table SNOWFLAKE. Grammar and other cases are fine.
  • sf.functions.regexp-instr: (b) required has no missing case: there is no o004; o005 only repeats the valid 'REGEXP_INSTR ( v1 , 'm' )' and no case omits the pattern, e.g. 'REGEXP_INSTR ( v1 )'. Grammar and outcomes are fine.
  • sf.functions.regexp-substr: (b) required has no missing case: there is no o004; o005 only repeats the valid 'REGEXP_SUBSTR ( v1 , 'm' )' and no case omits the pattern. Grammar matches docs; outcomes agree.
  • sf.functions.regexp-substr-all: (b) required has no missing case: there is no o004; o005 only repeats the valid 'REGEXP_SUBSTR_ALL ( v1 , 'm' )' and no case omits the pattern. Grammar matches docs; outcomes agree.
  • sf.functions.st-geogfromgeohash: (b) required has no missing case: there is no o002; o003 is the valid 'ST_GEOGFROMGEOHASH ( v1 )' and only has a missing case (o006). Grammar matches docs.
  • sf.functions.st-geohash: (b) the required <geography_expression> and <geometry_expression> have no missing case; o003/o009 are only the valid 'ST_GEOHASH ( 1 )' and only has missing cases (o006/o012). Grammar matches docs.
  • sf.functions.st-geomfromgeohash: (b) required has no missing case: there is no o002; o003 is the valid 'ST_GEOMFROMGEOHASH ( v1 )' and only has a missing case (o006). Grammar matches docs.
  • sf.functions.system-wait-for-openflow-connector-status: (b) the required first '<connector_name>' has no missing case: o008 is only the valid '( 1 , 'm' , 'm' )' and no case omits the name, e.g. '( 1 , 'm' )'. Grammar matches docs; outcomes agree.
  • sf.functions.system-wait-for-openflow-deployment-status: (b) the required first '<deployment_name>' has no missing case: o008 is only the valid '( 1 , 'm' , 'm' )' and no case omits the name, e.g. '( 1 , 'm' )'. Grammar matches docs; outcomes agree.
  • sf.functions.system-wait-for-openflow-runtime-status: (b) the required first '<runtime_name>' has no missing case: o008 is only the valid '( 1 , 'm' , 'm' )' and no case omits the name, e.g. '( 1 , 'm' )'. Grammar matches docs; outcomes agree.
  • sf.functions.system-wait-for-stable-openflow-deployments: (b) the required first '<deployment_name>' has no missing case: o005 is only the valid '( 1 , 'm' )' and no case omits it, e.g. '( 1 )'. Grammar matches docs; outcomes agree.
  • sf.functions.task-history: (a) the grammar ends '[, GRAPH_ID => ''] )' but the docs Syntax block also has '[, GRAPH_RUN_GROUP_ID => '' ]', so that option has no present, absent or missing cases. Other cases and outcomes are fine.
  • sf.functions.to-decimal.to-decimal: (b) required has no missing case: there is no o002; every case starts 'TO_DECIMAL ( 1', e.g. o003. The exemption covers only wrong-kind. Grammar matches docs; outcomes agree.
  • sf.functions.to-decimal.to-number: (b) required has no missing case: there is no o002; every case starts 'TO_NUMBER ( 1', e.g. o003. The exemption covers only wrong-kind. Grammar matches docs; outcomes agree.
  • sf.functions.to-decimal.to-numeric: (b) required has no missing case: there is no o002; every case starts 'TO_NUMERIC ( 1', e.g. o003. The exemption covers only wrong-kind. Grammar matches docs; outcomes agree.
  • sf.security_admin.alter-backup-policy.set: (b) SCHEDULE value '{ MINUTE | HOUR | USING CRON <time_zone> }': every case uses only '1 HOUR' (o010); MINUTE and USING CRON alternatives never exercised, and no missing or wrong-kind case for the SCHEDULE value
  • sf.security_admin.alter-user-add-key-pair: (d) omitted [ ] is invented as an empty name: o001/o005 "ALTER USER ADD KEY PAIR v1 PUBLIC_KEY = 'm'" tree has name {name:""}. Grammar, coverage and verdict/receipt agreement otherwise fine.
  • sf.security_admin.alter-user-add-programmatic-access-token: (d) omitted becomes empty name: o001 'ALTER USER ADD PROGRAMMATIC ACCESS TOKEN v1' tree name:"". Also [ IF NOT EXISTS ] survives only inside raw action string 'ADD PROGRAMMATIC ACCESS TOKEN IF NOT EXISTS' (o010), not a
  • sf.security_admin.alter-user-modify-programmatic-access-token.set: (d) omitted becomes empty name: o001 "ALTER USER MODIFY PROGRAMMATIC ACCESS TOKEN v1 SET COMMENT = 'm'" tree name:"". Token-level [ IF EXISTS ] only in raw action string 'MODIFY PROGRAMMATIC ACCESS TOKEN IF EXISTS SET'
  • sf.security_admin.alter-user-rotate-key-pair: (d) omitted [ ] is invented as an empty name: o001/o005 "ALTER USER ROTATE KEY PAIR v1 PUBLIC_KEY = 'm'" tree has name {name:""}. Grammar, coverage and verdict/receipt agreement otherwise fine.
  • sf.security_admin.alter-user-rotate-programmatic-access-token: (d) omitted becomes empty name: o001 'ALTER USER ROTATE PROGRAMMATIC ACCESS TOKEN v1' tree name:"". Token-level [ IF EXISTS ] only in raw action string 'ROTATE PROGRAMMATIC ACCESS TOKEN IF EXISTS' (o010), not a field.
  • sf.security_admin.create-backup-policy.backup-policy: (b) SCHEDULE value '{ MINUTE | HOUR | USING CRON <time_zone> }': only '1 HOUR' used (o023); MINUTE and USING CRON alternatives never exercised, no missing or wrong-kind case for the SCHEDULE value (snapshot poli
  • sf.security_admin.create-backup-policy.or-alter-backup-policy: (b) SCHEDULE value '{ MINUTE | HOUR | USING CRON <time_zone> }': only '1 HOUR' used (o007); MINUTE and USING CRON alternatives never exercised, no missing or wrong-kind case for the SCHEDULE value (snapshot poli
  • sf.security_admin.create-security-integration-oauth-snowflake.custom-oauth-client-type-oauth-redirect-uri: (b) <public_key1> and <public_key2> have no wrong-kind case: only missing (o090,o094) and quoted-key cases (o091,o095); no case puts e.g. an integer or name there. Note: 49 dossier trees are cut at 4000 chars (e.g. o002), limiting
  • sf.security_admin.create-security-integration-oauth-snowflake.oauth-redirect-uri: (b) <partner_application> has no wrong-kind case: only missing (o009) and LOOKER/TABLEAU_* values (o010,o099,o100); no case such as OAUTH_CLIENT = 'LOOKER' or = 1. Other operands, alternatives and verdict/receipt agreement fine.
  • sf.functions.try-to-decimal.try-to-decimal, .try-to-number, .try-to-numeric: approval withdrawn; same missing-argument gap as TO_DECIMAL, TO_NUMBER and TO_NUMERIC.
  • sf.security_admin.create-security-integration-api-auth.false: approval withdrawn; repeated <scope_2> has no missing case, the gap INFER_SCHEMA was rejected for.

6. Reviewer conflicts

  • Function arguments: one reviewer read the expression waiver as covering missing cases too and approved TRY_TO_DECIMAL/NUMBER/NUMERIC; another rejected TO_DECIMAL/NUMBER/NUMERIC for the same gap. The stricter reading is applied to both.
  • Repeated list items: one reviewer approved API_AUTHENTICATION false with a repeated <scope_2> that has no missing case; INFER_SCHEMA was rejected for that gap. The stricter reading is applied.

7. Spot-checked approvals

Each grammar matches its docs Syntax block, every case agrees with its receipt, and the new LIMIT 'x' case is a syntax error that the parser rejects.

8. Reachable forms after this change (621 catalogued forms unverified)

  • 101 review-only forms held by a rejection: name-operand gaps (the next change classifies them), missing cases for function arguments, raw-string or empty-name trees.
  • 174 forms needing parser or tree work, with receipts in hand.
  • 35 forms needing receipts.
  • 254 forms awaiting observation, mostly documented rows that Snowflake refuses.
  • 57 forms whose cases the capture guard holds or that cannot be verified: not reachable.

@kvlonge
kvlonge enabled auto-merge November 13, 2026 20:25
@kvlonge
kvlonge added this pull request to the merge queue Nov 13, 2026
Merged via the queue into main with commit 49c9028 Nov 13, 2026
9 checks passed
@kvlonge
kvlonge deleted the feat/syntax-pool-23 branch November 13, 2026 21:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant