SNOWFLAKE DOCS DIFF
総括は生成されていません（claude CLI が利用できなかった可能性があります）。
（この変更は要約対象外です。diff を参照してください）
判定根拠: SQL 構文/コードブロックの増減 (+21/-0)
--- ahttps://docs.snowflake.com/en/sql-reference/functions/convert_timezone+++ bhttps://docs.snowflake.com/en/sql-reference/functions/convert_timezone@@ -44,5 +44,7 @@ <dd> -For the 2-argument version, string specifying the timestamp to convert (can be any timestamp variant, including TIMESTAMP_NTZ).+For the 2-argument version, the timestamp to convert. Can be any timestamp variant (TIMESTAMP_LTZ,+TIMESTAMP_NTZ, or TIMESTAMP_TZ) or a DATE value. For how the source time zone is determined for each+of these types, see the usage notes below. </dd>@@ -64,6 +66,14 @@ - For the 3-argument version, the "wallclock" time in the result represents the same moment in time as the input "wallclock" in the input time zone, but in the target time zone.-- For the 2-argument version, the <code className="samp"><em>source_timestamp</em></code> argument typically includes the time zone. If the value- is of type TIMESTAMP_TZ, the time zone is taken from its value. Otherwise, the current session time zone is used.+- For the 2-argument version, the source time zone is determined by the data type of the+ <code className="samp"><em>source_timestamp</em></code> argument:++ - **TIMESTAMP_TZ:** The time zone is taken from the value itself.+ - **TIMESTAMP_LTZ:** The time zone is the current session time zone (set by the+ [](/sql-reference/parameters#label-timezone) parameter).+ - **TIMESTAMP_NTZ:** The value has no time zone, so it's interpreted as a "wallclock" time in the+ current session time zone, and that session time zone is used as the source.+ - **DATE:** The value is cast to TIMESTAMP_NTZ with the time set to midnight (`00:00:00`), and then+ handled the same way as TIMESTAMP_NTZ (the current session time zone is used as the source). - For <code className="samp"><em>source_tz</em></code> and <code className="samp"><em>target_tz</em></code>, you can specify a [time zone name](https://data.iana.org/time-zones/tzdb-2025b/zone1970.tab) or a [link name](https://data.iana.org/time-zones/tzdb-2025b/backward) from release %tzdb_version% of the [IANA Time Zone Database](https://www.iana.org/time-zones) (for example, `America/Los_Angeles`, `Europe/London`, `UTC`,@@ -167,2 +177,67 @@ +-------------------------------+-------------------------------+-------------------------------+-------------------------------+ ```++### Example with TIMESTAMP_LTZ input++The following example uses the 2-argument version with a TIMESTAMP_LTZ value. A TIMESTAMP_LTZ value is+interpreted in the current session time zone, so that session time zone is used as the source. The example+sets the session time zone to `America/Los_Angeles` first:++```sql+ALTER SESSION SET TIMEZONE = 'America/Los_Angeles';+```++Convert a TIMESTAMP_LTZ value to UTC. The input `09:00:00` is interpreted in the session time zone+(`America/Los_Angeles`, which is seven hours behind UTC), so the result is offset accordingly:++```sql+SELECT CONVERT_TIMEZONE('UTC', '2024-04-05 09:00:00'::TIMESTAMP_LTZ) AS ltz_in_utc;+```++```text++-------------------------------++| LTZ_IN_UTC |+|-------------------------------|+| 2024-04-05 16:00:00.000 +0000 |++-------------------------------++```++### Examples with TIMESTAMP_NTZ and DATE input++The following examples use the 2-argument version with a TIMESTAMP_NTZ value and a DATE value. Because+neither type carries a time zone, the current session time zone is used as the source time zone. These+examples set the session time zone to `America/Los_Angeles` first:++```sql+ALTER SESSION SET TIMEZONE = 'America/Los_Angeles';+```++Convert a TIMESTAMP_NTZ value to UTC. The input is interpreted as a "wallclock" time in the session+time zone (`America/Los_Angeles`), so the result is offset accordingly:++```sql+SELECT CONVERT_TIMEZONE('UTC', '2024-04-05 12:00:00'::TIMESTAMP_NTZ) AS ntz_in_utc;+```++```text++-------------------------------++| NTZ_IN_UTC |+|-------------------------------|+| 2024-04-05 19:00:00.000 +0000 |++-------------------------------++```++Convert a DATE value to UTC. The DATE is cast to TIMESTAMP_NTZ at midnight in the session time zone+(`America/Los_Angeles`), then converted:++```sql+SELECT CONVERT_TIMEZONE('UTC', '2024-04-05'::DATE) AS date_in_utc;+```++```text++-------------------------------++| DATE_IN_UTC |+|-------------------------------|+| 2024-04-05 07:00:00.000 +0000 |++-------------------------------++```
（この変更は要約対象外です。diff を参照してください）
判定根拠: SQL 構文/コードブロックの増減 (+11/-1)
--- ahttps://docs.snowflake.com/en/sql-reference/functions/st_buffer+++ bhttps://docs.snowflake.com/en/sql-reference/functions/st_buffer@@ -65,17 +65,72 @@ ``` -The following example returns a Polygon around a Point with a radius of one:+### Buffer a Point++Buffering a Point returns a MultiPolygon that approximates a circle around the Point. Because ST_BUFFER uses eight+segments to approximate each quarter circle, the circle is drawn with 32 straight segments (33 points, because the ring+repeats its starting point). The area is therefore slightly smaller than the area of a true circle+(`PI() * 1 * 1`, or about `3.1416`).++The following example buffers a Point by a distance of `1` and reports the number of points and the area of the result: ```sql-SELECT ST_BUFFER(TO_GEOMETRY('POINT(0 0)'), 1) AS geom;+SELECT ST_NPOINTS(buffer) AS num_points,+ ST_AREA(buffer) AS area+ FROM (SELECT ST_BUFFER(TO_GEOMETRY('POINT(0 0)'), 1) AS buffer); ``` ```text-+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-| GEOM |-|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-| MULTIPOLYGON(((1 0,0.9807852804 -0.195090322,0.9238795325 -0.3826834324,0.8314696123 -0.555570233,0.7071067812 -0.7071067812,0.555570233 -0.8314696123,0.3826834324 -0.9238795325,0.195090322 -0.9807852804,6.123233996e-17 -1,-0.195090322 -0.9807852804,-0.3826834324 -0.9238795325,-0.555570233 -0.8314696123,-0.7071067812 -0.7071067812,-0.8314696123 -0.555570233,-0.9238795325 -0.3826834324,-0.9807852804 -0.195090322,-1 7.657137398e-16,-0.9807852804 0.195090322,-0.9238795325 0.3826834324,-0.8314696123 0.555570233,-0.7071067812 0.7071067812,-0.555570233 0.8314696123,-0.3826834324 0.9238795325,-0.195090322 0.9807852804,2.480838239e-15 1,0.195090322 0.9807852804,0.3826834324 0.9238795325,0.555570233 0.8314696123,0.7071067812 0.7071067812,0.8314696123 0.555570233,0.9238795325 0.3826834324,0.9807852804 0.195090322,1 0))) |-+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+++------------+-------------------++| NUM_POINTS | AREA |+|------------+-------------------|+| 33 | 3.121445152258052 |++------------+-------------------+ ```++To see the full shape, select the buffer directly (for example, `SELECT ST_BUFFER(TO_GEOMETRY('POINT(0 0)'), 1)`).+The output is a MultiPolygon with a long list of coordinates for the 32 segments that approximate the circle.++### Buffer a LineString++ST_BUFFER buffers a LineString on both sides and uses round endcaps, so the result is a capsule-shaped MultiPolygon.+The following example buffers a line that is 10 units long by a distance of `2`:++```sql+SELECT ST_NPOINTS(buffer) AS num_points,+ ST_AREA(buffer) AS area+ FROM (SELECT ST_BUFFER(TO_GEOMETRY('LINESTRING(0 0, 10 0)'), 2) AS buffer);+```++```text++------------+--------------------++| NUM_POINTS | AREA |+|------------+--------------------|+| 36 | 52.485780609032204 |++------------+--------------------++```++The area is the rectangle along the line (10 units long and 4 units wide, for 40 square units) plus the two rounded ends,+which together approximate a circle with a radius of `2`.++### Specify the distance in meters++The units of <code className="samp"><em>distance</em></code> depend on the SRID of the input object. The following example+buffers a Point in SRID 32633 (UTM zone 33N, which uses meters) by `100` meters. The resulting area is close to the area+of a circle with a 100-meter radius (`PI() * 100 * 100`, or about `31416` square meters):++```sql+SELECT ST_AREA(buffer) AS area_sq_meters+ FROM (SELECT ST_BUFFER(TO_GEOMETRY('SRID=32633;POINT(0 0)'), 100) AS buffer);+```++```text++--------------------++| AREA_SQ_METERS |+|--------------------|+| 31214.45152258053 |++--------------------++```++### Shrink a shape with a negative distance The following example uses a negative value for <code className="samp"><em>distance</em></code> to remove small irregularities (such as spikes) from the shape.
（この変更は要約対象外です。diff を参照してください）
判定根拠: SQL 構文/コードブロックの増減 (+10/-0)
--- ahttps://docs.snowflake.com/en/sql-reference/data-types-logical+++ bhttps://docs.snowflake.com/en/sql-reference/data-types-logical@@ -115,4 +115,9 @@ </dd> </dl>++Implicit conversion to a text string works for BOOLEAN literals and BOOLEAN columns. A computed BOOLEAN expression, such as a+comparison like `(0 = 1)`, isn't implicitly converted when you use it directly with the concatenation operator (`||`), so the query+returns an error. To concatenate the result of a BOOLEAN expression, cast it to a string explicitly with+[TO_VARCHAR](/sql-reference/functions/to_char) or the `::VARCHAR` operator. ## Examples@@ -231,2 +236,28 @@ +----------------------+-------------------------+ ```++Concatenating a computed BOOLEAN expression directly returns an error, because the expression isn't implicitly converted to a+text string:++```sql+SELECT 'A' || (0 = 1);+```++```text+001044 (42P13): SQL compilation error: error line 1 at position 25+Invalid argument types for function '||': (VARCHAR(1), BOOLEAN)+```++To concatenate the result, cast the BOOLEAN expression to a string explicitly:++```sql+SELECT 'A' || TO_VARCHAR(0 = 1);+```++```text++--------------------------++| 'A' || TO_VARCHAR(0 = 1) |+|--------------------------|+| Afalse |++--------------------------++```
（この変更は要約対象外です。diff を参照してください）
判定根拠: SQL 構文/コードブロックの増減 (+5/-0)
--- ahttps://docs.snowflake.com/en/sql-reference/functions/mod+++ bhttps://docs.snowflake.com/en/sql-reference/functions/mod@@ -72,2 +72,31 @@ </blockquote>++The following steps show how each result is calculated. Because `MOD()` uses truncation-based division+(rounding the quotient toward zero), the remainder is `expr1 - (TRUNC(expr1 / expr2) * expr2)`:++- `MOD(3, 2)`: `3 / 2` is `1.5`, which truncates to `1`. The remainder is `3 - (1 * 2) = 1`.+- `MOD(4.5, 1.2)`: `4.5 / 1.2` is `3.75`, which truncates to `3`. The remainder is `4.5 - (3 * 1.2) = 4.5 - 3.6 = 0.9`.++Because `MOD()` uses truncation-based division, a negative <code className="samp"><em>expr1</em></code> produces a negative+remainder:++<blockquote>++```sql+SELECT MOD(-3, 2) AS neg_mod;+```++Output:++```sql++---------++| NEG_MOD |++---------++| -1 |++---------++```++</blockquote>++`MOD(-3, 2)`: `-3 / 2` is `-1.5`, which truncates to `-1`. The remainder is `-3 - (-1 * 2) = -3 + 2 = -1`.
（この変更は要約対象外です。diff を参照してください）
判定根拠: SQL 構文/コードブロックの増減 (+0/-3)
--- ahttps://docs.snowflake.com/en/user-guide/tables-iceberg-data-types+++ bhttps://docs.snowflake.com/en/user-guide/tables-iceberg-data-types@@ -267,7 +267,4 @@ Inserting a value that doesn't exactly match L bytes in length results in an error. -To use the `fixed(L)` data type, you must enable the 2026_02 behavior-change bundle in your account. For instructions on-how to enable this bundle, see [](#label-tables-iceberg-data-types-fixed-binary).- </td> </tr>@@ -278,7 +275,4 @@ The default size is 64 MB, and the only size that you can specify explicitly is 67108864 (64 MB).--To use the `binary` data type, you must enable the 2026_02 behavior-change bundle in your account. For instructions on-how to enable this bundle, see [](#label-tables-iceberg-data-types-fixed-binary). </td>@@ -302,16 +296,4 @@ </div>--<a id="label-tables-iceberg-data-types-fixed-binary"></a>--#### Use the Iceberg `fixed(L)` or `binary` primitive data types--To use the Iceberg `fixed(L)` or `binary` primitive data types, you must enable the 2026_02 behavior-change bundle in your account.--To [enable this bundle in your account](#label-manage-bcr-enable-bundle), execute the following statement:--```sql-SELECT SYSTEM$ENABLE_BEHAVIOR_CHANGE_BUNDLE('2026_02');-``` <a id="label-tables-iceberg-v3-data-types"></a>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（146行追加・0行削除）
--- ahttps://docs.snowflake.com/en/migrations/snowconvert-docs/general/release-notes/release-notes/README+++ bhttps://docs.snowflake.com/en/migrations/snowconvert-docs/general/release-notes/release-notes/README@@ -2,4 +2,150 @@ The SnowConvert AI tool is subject to the [Conversion Software Terms of Use](https://www.snowflake.com/en/legal/technical-services-and-education/conversion-software-terms/).++## Version 2.40.1 (Aug 13, 2026)++### CLI++#### New Features++- Added Apache Druid as a code-conversion-only dialect.++#### Improvements++- Scoped DEW worker configuration to the project level and added connection-name template support.+- Added forwarding of `useSnowpipeForResults` from Data Validation workflow configuration to the orchestrator.+- Unified DMVF subprocess logs under `scai logs` for streamlined troubleshooting.+- Added preservation of per-column `COLLATE` settings during Redshift extraction.+- Added `--json` output for per-check results from `scai data-doctor` on check failure.++#### Bug Fixes++- Fixed an issue where `localhost` was not normalized to IPv4 loopback for SQL Server data validation sources.++### Desktop App++#### Improvements++- Updated the Cortex Code migration promotion to reference Snowflake AIM for Data Warehouses preview and link to the request form.++### Conversion Engine++#### New Features++##### Oracle++- Added translation of record-field associative element access via `OBJECT`.+- Added parsing of `$IF`/`$THEN`/`$END` conditional compilation on procedure and function headers.+- Added translation of `SYS_CONTEXT('USERENV','SID')` to `CURRENT_SESSION()`.+- Added translation of dense collection element writes and `EXTEND` to array rebuilds.+- Added translation of collection operations on built-in package types (`DBMS_SQL.VARCHAR2A`, `UTL_HTTP.COOKIE_TABLE`).+- Added support for label-qualified variable references (`label.var`) in Snowflake Scripting output.+- Added translation of dense `coll(i).EXTEND` and deconflicted bare `EXTEND` EWI emission.++##### Power BI++- Added multi-database detection and splicing for Teradata-sourced Power BI repointing.+- Added recognition of bare Teradata base-connection expressions.+- Added recognition of dependent connection references for Teradata sources.++#### Bug Fixes++##### Oracle++- Fixed parsing of `MATCH_RECOGNIZE` for cursor and `SELECT` pass-through.+- Fixed parsing of `RECORD` field `NULL`/`NOT NULL` constraints.+- Fixed parsing of empty `PACKAGE BODY` declarations.+- Fixed handling of `SET TRANSACTION` statements (now removed with `SSC-FDM-0027`).+- Fixed parsing of `XMLELEMENT(NAME ...)` so `FORALL INSERT VALUES` succeeds.+- Fixed handling of `MODEL` clause (now kept with `SSC-EWI-OR0042`).+- Fixed parsing of `FOR UPDATE` before `ORDER BY`.+- Fixed `ALTER TRIGGER` to use `SSC-FDM-OR0084` instead of generic `SSC-EWI-0073`.+- Fixed parsing of collection methods on indexed elements.+- Fixed parsing and transformation of `JSON_OBJECT(AGG)` value form.+- Fixed parsing of function-based and expression `CREATE INDEX` keys.+- Fixed parsing of `XMLELEMENT(EVALNAME)` and added `OR0016` null stub.+- Fixed null-guard for `GetSinglePartitionTarget` when `FromClause.Tables` is null.+- Fixed parsing and wrapping of bare table functions in `FROM` clauses.+- Fixed null-safe `SqlObjectCollector` name resolution.+- Fixed `UPDATE (subquery) SET` crash on select aliases.+- Fixed package-level associative-array element write aborting file generation.+- Fixed parsing of `XMLSERIALIZE(... INDENT)` and mapped to `TO_VARCHAR`.+- Fixed `SSC-EWI-0013` on `DATE + INTERVAL` inside procedures.++##### Teradata++- Fixed `COLLATE`-wrapping of non-character operands in case-sensitivity comparisons.++##### SQL Server++- Improved mining of row-count and `EXISTS` gates as cardinality predicates.++##### General++- Fixed empty scope stack guard in `SymbolResolver.OpenScope`.++### Data Validation++#### New Features++- Added support for geographic and geometry data types in data migration and validation for SQL Server, PostgreSQL, and Teradata.++#### Improvements++- Added a warning for unrecognized `configuration.toml` keys in the data exchange agent.+- Added backward compatibility for IPv4 address handling.+- Added in-warehouse L3 SQL cell fall-through for mismatched keys.+- Added Redshift `TIME` type mapping in Data Validation seed Snowflake DDL.+- Made task-queue batch inserts transactional.+- Added a guard to claim only tables owned by a specific workflow.+- Reconciled PostgreSQL type mappings for `MONEY`, `BIT*`, and `OID`.+- Reconciled Teradata type mappings for `PERIOD`, `XML`, `CLOB`, and `TIMESTAMP WITH TIME ZONE`.++#### Bug Fixes++- Fixed ordinal position warning in schema validation.+- Fixed an issue where partitions with `NULL` boundary values were not handled correctly.+- Fixed an issue where `indexColumnList` was not respecting casing and column renames.++### Others++#### Migration Plugin++##### New Features++- Added anti-patterns assessment API endpoints.+- Added Data Migration & Validation journey page to the Assessment dashboard.+- Added Testing journey content page to the Assessment dashboard.+- Added Object Exclusion Report View with category-based exclusion recommendations.++##### Improvements++- Simplified data migration workflow confirmation prompt labels.++##### Bug Fixes++- Fixed duplicate ETL registry entries by importing at register time instead of convert time.+- Fixed dashboard reporting in-progress tasks as completed.+- Fixed convert dead-end for untyped object types.++#### Testing Framework++##### New Features++- Added a coverage report writer with multiple renderers.++##### Bug Fixes++- Fixed reading of converted ETL orchestration DDL under the `_etl` root so task names resolve correctly.++#### Code Unit Registry++##### New Features++- Made user-initiated registry renames durable on Windows.++##### Bug Fixes++- Fixed directory `fsync` skip on Windows in registry sync operations. ## Version 2.40.0 (Aug 11, 2026)
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（17行追加・17行削除）
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/aisql-regional-availability+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/aisql-regional-availability@@ -26,5 +26,5 @@ and will give you a good idea what a state-of-the-art model can do. -- `claude-opus-5` (Public Preview) is Anthropic's flagship Claude Opus model, with improved performance on coding, long-horizon agentic work, and professional tasks like document drafting and data analysis. With a 1,000,000-token context window and up to 128,000 output tokens, it can analyze large document collections and produce detailed responses in a single call.+- `claude-opus-5` is Anthropic's flagship Claude Opus model, with improved performance on coding, long-horizon agentic work, and professional tasks like document drafting and data analysis. With a 1,000,000-token context window and up to 128,000 output tokens, it can analyze large document collections and produce detailed responses in a single call. - `claude-opus-4-8` is Anthropic's Claude Opus model, built for advanced reasoning, long-running agentic workflows, and complex coding tasks. With a 1,000,000-token context window and up to 128,000 output tokens, it can analyze large document collections and produce detailed responses in a single call. - `gemini-3.1-pro` (Public Preview) is Google's most capable Gemini model available in Snowflake Cortex, suited for advanced reasoning and multimodal tasks. It supports up to 64,000 output tokens and requires [cross-region inference](#label-use-cross-region-inference).@@ -191,6 +191,6 @@ <td></td> <td>%cm%</td>- <td>%cm%</td>- <td>%cm%</td>+ <td></td>+ <td></td> <td></td> <td></td>@@ -203,16 +203,16 @@ <td></td> <td>\*</td>+ <td></td>+ <td></td>+ <td></td>+ <td></td>+ <td></td>+ </tr>+ <tr>+ <td>`claude-opus-4-8`</td> <td>\*</td>- <td></td>- <td></td>- <td></td>- <td></td>- </tr>- <tr>- <td>`claude-opus-4-8`</td>- <td>%cm%</td>- <td>%cm%</td>- <td></td>- <td>%cm%</td>+ <td>\*</td>+ <td></td>+ <td>\*</td> <td></td> <td></td>@@ -240,5 +240,5 @@ <td>%cm%</td> <td>%cm%</td>- <td></td>+ <td>%cm%</td> <td></td> <td></td>@@ -264,5 +264,5 @@ <td>%cm%</td> <td>%cm%</td>- <td></td>+ <td>%cm%</td> <td></td> <td></td>@@ -288,5 +288,5 @@ <td>%cm%</td> <td>%cm%</td>- <td></td>+ <td>%cm%</td> <td></td> <td></td>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（22行追加・0行削除）
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-rest-api+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-rest-api@@ -342,4 +342,15 @@ <tbody> <tr>+ <td>`claude-sonnet-5`</td>+ <td>%cm%</td>+ <td>%cm%</td>+ <td>%cm%</td>+ <td>%cm%</td>+ <td></td>+ <td></td>+ <td></td>+ <td></td>+ </tr>+ <tr> <td>`claude-opus-5`</td> <td>\*</td>@@ -347,5 +358,16 @@ <td>\*</td> <td>\*</td>+ <td></td>+ <td></td>+ <td></td>+ <td></td>+ </tr>+ <tr>+ <td>`claude-opus-4-8`</td> <td>\*</td>+ <td>\*</td>+ <td>\*</td>+ <td>\*</td>+ <td></td> <td></td> <td></td>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（13行追加・1行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/functions/object_agg+++ bhttps://docs.snowflake.com/en/sql-reference/functions/object_agg@@ -50,4 +50,11 @@ ## Examples +These examples build a table of key-value pairs, then use OBJECT_AGG to collect the pairs in each+group into a single OBJECT (for example, gathering a person's attributes into one object per person).++First, create and populate a table. The value column is typed as VARIANT because the+<code className="samp"><em>value</em></code> argument of OBJECT_AGG must be a VARIANT, so each inserted value is+cast with `::VARIANT`:+ ```sql CREATE OR REPLACE TABLE objectagg_example(g NUMBER, k VARCHAR(30), v VARIANT);@@ -71,5 +78,6 @@ ``` -This example uses OBJECT_AGG as an aggregate function:+This example uses OBJECT_AGG as an aggregate function. Grouping by `g` produces one OBJECT per group,+where each `k` value becomes a key and its `v` value becomes the corresponding value: ```sql@@ -92,4 +100,8 @@ ``` +The following example is optional and shows how to expand the aggregated objects back into rows. It+passes the OBJECT produced by OBJECT_AGG to [](/sql-reference/functions/flatten), which returns one+row for each key-value pair in each object:+ ```sql SELECT seq, key, value
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（14行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/account-usage+++ bhttps://docs.snowflake.com/en/sql-reference/account-usage@@ -862,4 +862,11 @@ </tr> <tr>+ <td>[POSTGRES_COMPUTE_USAGE_HISTORY](/sql-reference/account-usage/postgres_compute_usage_history)</td>+ <td>Historical</td>+ <td>3 hours</td>+ <td></td>+ <td>Data retained for 1 year.</td>+ </tr>+ <tr> <td>[POSTGRES_STORAGE_USAGE_HISTORY](/sql-reference/account-usage/postgres_storage_usage_history)</td> <td>Historical</td>@@ -2113,4 +2120,11 @@ </td> <td>GOVERNANCE_VIEWER, SECURITY_VIEWER</td>+ </tr>+ <tr>+ <td>+ [POSTGRES_COMPUTE_USAGE_HISTORY+ view](/sql-reference/account-usage/postgres_compute_usage_history)+ </td>+ <td>USAGE_VIEWER</td> </tr> <tr>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・8行削除）
--- ahttps://docs.snowflake.com/en/user-guide/data-engineering/dbt-projects-on-snowflake-environment-variables+++ bhttps://docs.snowflake.com/en/user-guide/data-engineering/dbt-projects-on-snowflake-environment-variables@@ -635,20 +635,16 @@ ### Spin up an isolated per-PR database for CI testing (GitHub Actions) -This example uses a PR number to spin up an isolated staging database, run transformations on it, and clean up.+This example uses a PR number to spin up an isolated staging database, run transformations on it, and clean it up. GitHub Actions replaces `${{ github.event.number }}` with the PR number before the shell runs. ```bash-# In a CI GitHub Action, add the PR number as an env var.-env:- PR_NUMBER: ${{ github.event.number }}- # Deploy a tester object. snow dbt deploy tester_tasty_bytes_dbt_project --source ./tasty_bytes # Create a staging database using the PR number.-snow sql -q "CREATE DATABASE tasty_bytes_staging_${PR_NUMBER}_db CLONE tasty_bytes_dbt_db"+snow sql -q "CREATE DATABASE tasty_bytes_staging_pr_${{ github.event.number }}_db CLONE tasty_bytes_dbt_db" # Execute against the staging database with overrides. snow dbt execute --env staging \- --env-vars '{"DBT_DATABASE": "tasty_bytes_staging_${PR_NUMBER}_db"}' tester_tasty_bytes_dbt_project run+ --env-vars '{"DBT_DATABASE": "tasty_bytes_staging_pr_${{ github.event.number }}_db"}' tester_tasty_bytes_dbt_project run # After the PR merges, deploy to the production object and select the environment for compilation and subsequent runs.@@ -656,5 +652,5 @@ # Clean up using the same PR number.-snow sql -q "DROP DATABASE IF EXISTS tasty_bytes_staging_${PR_NUMBER}_db"+snow sql -q "DROP DATABASE IF EXISTS tasty_bytes_staging_pr_${{ github.event.number }}_db" ```
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（6行追加・1行削除）
--- ahttps://docs.snowflake.com/en/user-guide/interactive+++ bhttps://docs.snowflake.com/en/user-guide/interactive@@ -631,12 +631,17 @@ - `us-east-2` - AWS US East (Ohio) - `ca-central-1` - AWS Canada (Central)+- `sa-east-1` - AWS South America (São Paulo) - `af-south-1` - AWS Africa (Cape Town) - `ap-northeast-1` - AWS Asia Pacific (Tokyo)+- `ap-northeast-2` - AWS Asia Pacific (Seoul) - `ap-northeast-3` - AWS Asia Pacific (Osaka)+- `ap-south-1` - AWS Asia Pacific (Mumbai)+- `ap-southeast-1` - AWS Asia Pacific (Singapore) - `ap-southeast-2` - AWS Asia Pacific (Sydney)-- `sa-east-1` - AWS South America (São Paulo) - `eu-central-1` - AWS EU (Frankfurt)+- `eu-north-1` - AWS EU (Stockholm) - `eu-west-1` - AWS EU (Ireland) - `eu-west-2` - AWS Europe (London)+- `eu-west-3` - AWS Europe (Paris) - `us-central1` - GCP US Central1 (Iowa) - `us-east4` - GCP US East4 (N. Virginia)
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（5行追加・2行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/functions/h3_grid_disk+++ bhttps://docs.snowflake.com/en/sql-reference/functions/h3_grid_disk@@ -17,5 +17,6 @@ Returns an [array](#label-data-type-array) of the IDs of the [H3](#label-data-types-geospatial-h3) cells that-are within the k-distance from the specified cell. The IDs in the returned ARRAY are INTEGER values (if an INTEGER+are within the specified grid distance (`k_value`) of the given cell. The grid distance, often written as `k` in the H3+model, is the number of steps between cells in the H3 grid. The IDs in the returned ARRAY are INTEGER values (if an INTEGER value was provided as the input ID) or VARCHAR values containing the hexadecimal IDs (if a hexadecimal ID was provided as the input ID).@@ -39,5 +40,7 @@ <dd> -An INTEGER that represents the grid distance. You must specify a non-negative value.+An INTEGER that represents the grid distance `k`: the number of steps between cells in the H3 grid. You must specify a+non-negative value. For example, `0` returns only the specified cell, and `1` returns that cell plus its immediate+neighbors. </dd>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（7行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/snowflake-db-roles+++ bhttps://docs.snowflake.com/en/sql-reference/snowflake-db-roles@@ -622,4 +622,11 @@ </td> <td>GOVERNANCE_VIEWER, SECURITY_VIEWER</td>+ </tr>+ <tr>+ <td>+ [POSTGRES_COMPUTE_USAGE_HISTORY+ view](/sql-reference/account-usage/postgres_compute_usage_history)+ </td>+ <td>USAGE_VIEWER</td> </tr> <tr>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（6行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage@@ -367,4 +367,10 @@ </tr> <tr>+ <td>[POSTGRES_COMPUTE_USAGE_HISTORY](/sql-reference/organization-usage/postgres_compute_usage_history)</td>+ <td>Historical</td>+ <td>24 hours</td>+ <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account). Data retained for 1 year.</td>+ </tr>+ <tr> <td>[PROCEDURES](/sql-reference/organization-usage/procedures)</td> <td>Object</td>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（6行追加・0行削除）
--- ahttps://docs.snowflake.com/en/user-guide/warehouses-adaptive+++ bhttps://docs.snowflake.com/en/user-guide/warehouses-adaptive@@ -125,5 +125,7 @@ - EU Central 1 (Frankfurt)+- EU North 1 (Stockholm) - EU West 1 (Ireland)+- EU West 3 (Paris) - Europe (London) @@ -131,5 +133,7 @@ - AP Northeast 1 (Tokyo)+- AP Northeast 2 (Seoul) - AP Northeast 3 (Osaka)+- AP South 1 (Mumbai) - AP Southeast 2 (Sydney) @@ -144,6 +148,8 @@ - Canada Central - Central US (Iowa)+- East US - East US 2 (Virginia) - Mexico Central+- South Central US (Texas) - West US 2
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（5行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/data-types-text+++ bhttps://docs.snowflake.com/en/sql-reference/data-types-text@@ -37,4 +37,9 @@ If no length is specified, the default is 16777216.++The 16777216 default applies to columns created through SQL DDL. Some clients create VARCHAR columns+at the maximum length instead. For example, when Snowpark infers a table's schema (such as when you+save a DataFrame with an inferred schema), it creates string columns as `VARCHAR(134217728)`. In that+case, `INFORMATION_SCHEMA.COLUMNS` reports a `CHARACTER_MAXIMUM_LENGTH` of 134217728, not 16777216. Although a VARCHAR value's maximum length is specified in <span className="emph">characters</span>, a VARCHAR value is also limited to a maximum of
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-database+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-database@@ -990,5 +990,6 @@ - Databases created from shares differ from standard databases in the following ways:- - They do not have the PUBLIC or INFORMATION_SCHEMA schemas unless these schemas were explicitly granted to the share.+ - They do not have the PUBLIC schema unless it was explicitly granted to the share. They do include the+ INFORMATION_SCHEMA schema automatically. - They cannot be cloned. - Properties, such as `TRANSIENT` and `DATA_RETENTION_TIME_IN_DAYS`, do not apply.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/data-types-datetime+++ bhttps://docs.snowflake.com/en/sql-reference/data-types-datetime@@ -1196,5 +1196,5 @@ <p><sub>[1] The number of digits describes the output produced when serializing values to text. When parsing text, Snowflake accepts up to the specified number of digits. For example, a day number can be one or two digits.</sub></p> -<p><sub>[2] The number of digits describes the output produced when serializing values to text. Parsing isn't supported. If parsing is required, use an equivalent format that includes leading zeros. These format elements will be enabled in BCR bundle 2026_03.</sub></p>+<p><sub>[2] The number of digits describes the output produced when serializing values to text: values are serialized without leading zeros. When parsing text, Snowflake accepts one or two digits.</sub></p> <p><sub>[3] For the MON format element, the output produced when serializing values to text is the abbreviated month name. For the MMMM format element, the output produced when serializing values to text is the full month name. When parsing text, Snowflake accepts the three-digit abbreviation or the full month name for both MON and MMMM. For example, "January" or "Jan", "February" or "Feb", and so on are accepted when parsing text.</sub></p>
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/date-time-input-output+++ bhttps://docs.snowflake.com/en/sql-reference/date-time-input-output@@ -297,5 +297,5 @@ <p><sub>[1] The number of digits describes the output produced when serializing values to text. When parsing text, Snowflake accepts up to the specified number of digits. For example, a day number can be one or two digits.</sub></p> -<p><sub>[2] The number of digits describes the output produced when serializing values to text. Parsing isn't supported. If parsing is required, use an equivalent format that includes leading zeros. These format elements will be enabled in BCR bundle 2026_03.</sub></p>+<p><sub>[2] The number of digits describes the output produced when serializing values to text: values are serialized without leading zeros. When parsing text, Snowflake accepts one or two digits.</sub></p> <p><sub>[3] For the MON format element, the output produced when serializing values to text is the abbreviated month name. For the MMMM format element, the output produced when serializing values to text is the full month name. When parsing text, Snowflake accepts the three-digit abbreviation or the full month name for both MON and MMMM. For example, "January" or "Jan", "February" or "Feb", and so on are accepted when parsing text.</sub></p>
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-security-integration-oauth-external+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-security-integration-oauth-external@@ -147,5 +147,5 @@ - RSA digital signature algorithms RS256, RS384, and RS512.-- Elliptic Curve Digital Signature Algorithms (ECDSA) algorithms ES256 (P-256), ES384 (P-384), and ES512 (P-521).+- (Python driver only) Elliptic Curve Digital Signature Algorithms (ECDSA) algorithms ES256 (P-256), ES384 (P-384), and ES512 (P-521). These signatures use the SHA-256, SHA-384, and SHA-512 hash algorithms, respectively.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/functions/array_position+++ bhttps://docs.snowflake.com/en/sql-reference/functions/array_position@@ -15,5 +15,5 @@ ```sqlsyntax-ARRAY_POSITION( <variant_expr> , <array> )+ARRAY_POSITION( <value_expr> , <array> ) ```
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-postgres/postgres-terraform+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-postgres/postgres-terraform@@ -127,5 +127,5 @@ The port is always 5432 unless you're using [connection pooling](/user-guide/snowflake-postgres/postgres-connection-pooling), which uses-port 6432. Credentials aren't available through Terraform and must be+port 5431. Credentials aren't available through Terraform and must be configured separately:
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-postgres/postgres-cost+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-postgres/postgres-cost@@ -23,4 +23,6 @@ You can view the total compute usage for Snowflake Postgres instances by querying the following views: +- You can query the [](/sql-reference/account-usage/postgres_compute_usage_history) to see the hourly credit usage across all+ Snowflake Postgres instances for an account within the last 365 days (1 year). - You can query the [](/sql-reference/account-usage/metering_history) and specify `service_type IN ('POSTGRES_COMPUTE', 'POSTGRES_COMPUTE_HA')` in the WHERE clause to see the hourly credit usage across all Snowflake Postgres instances for an account within the last 365 days (1 year).
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/key-pair-auth+++ bhttps://docs.snowflake.com/en/user-guide/key-pair-auth@@ -55,5 +55,5 @@ - RSA digital signature algorithms RS256, RS384, and RS512.-- Elliptic Curve Digital Signature Algorithms (ECDSA) algorithms ES256 (P-256), ES384 (P-384), and ES512 (P-521).+- (Python driver only) Elliptic Curve Digital Signature Algorithms (ECDSA) algorithms ES256 (P-256), ES384 (P-384), and ES512 (P-521). These signatures use the SHA-256, SHA-384, and SHA-512 hash algorithms, respectively.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/functions-conversion+++ bhttps://docs.snowflake.com/en/sql-reference/functions-conversion@@ -392,5 +392,5 @@ <p><sub>[1] The number of digits describes the output produced when serializing values to text. When parsing text, Snowflake accepts up to the specified number of digits. For example, a day number can be one or two digits.</sub></p> -<p><sub>[2] The number of digits describes the output produced when serializing values to text. Parsing isn't supported. If parsing is required, use an equivalent format that includes leading zeros. These format elements will be enabled in BCR bundle 2026_03.</sub></p>+<p><sub>[2] The number of digits describes the output produced when serializing values to text: values are serialized without leading zeros. When parsing text, Snowflake accepts one or two digits.</sub></p> <p><sub>[3] For the MON format element, the output produced when serializing values to text is the abbreviated month name. For the MMMM format element, the output produced when serializing values to text is the full month name. When parsing text, Snowflake accepts the three-digit abbreviation or the full month name for both MON and MMMM. For example, "January" or "Jan", "February" or "Feb", and so on are accepted when parsing text.</sub></p>
| セクション | S | A | B | C | 計 |
|---|---|---|---|---|---|
| SQL Functions | 0 | 3 | 2 | 1 | 6 |
| SQL General Reference | 0 | 1 | 2 | 3 | 6 |
| User Guide | 0 | 1 | 3 | 1 | 5 |
| Snowflake Cortex (AI & ML) | 0 | 0 | 2 | 0 | 2 |
| SQL Commands | 0 | 0 | 0 | 2 | 2 |
| Snowflake Postgres | 0 | 0 | 0 | 2 | 2 |
| Migrations | 0 | 0 | 1 | 0 | 1 |
| Account Usage | 0 | 0 | 1 | 0 | 1 |
| Organization Usage | 0 | 0 | 1 | 0 | 1 |