From 6afdcba1772653fa5b1ec8bdd7e8e6b4431d6041 Mon Sep 17 00:00:00 2001 From: josh-wong Date: Wed, 10 Sep 2025 02:46:31 +0000 Subject: [PATCH] AUTO: Sync ScalarDB docs in English to docs site repo --- versioned_docs/version-3.15/scalardb-sql/grammar.mdx | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/versioned_docs/version-3.15/scalardb-sql/grammar.mdx b/versioned_docs/version-3.15/scalardb-sql/grammar.mdx index 1d26b661..6e8ab178 100644 --- a/versioned_docs/version-3.15/scalardb-sql/grammar.mdx +++ b/versioned_docs/version-3.15/scalardb-sql/grammar.mdx @@ -552,6 +552,16 @@ DropCoordinatorTablesStatement statement2 = The `ALTER TABLE` command alters a table (ex. adding a column). +:::warning + +You should carefully consider adding a new column to a table because the execution time may vary greatly depending on the underlying storage. Please plan accordingly and consider the following, especially if the database runs in production: + +- **For Cosmos DB for NoSQL and DynamoDB:** Adding a column is almost instantaneous as the table schema is not modified. Only the table metadata stored in a separate table is updated. +- **For Cassandra:** Adding a column will only update the schema metadata and will not modify the existing schema records. The cluster topology is the main factor for the execution time. Changes to the schema metadata are shared to each cluster node via a gossip protocol. Because of this, the larger the cluster, the longer it will take for all nodes to be updated. +- **For relational databases (MySQL, Oracle, etc.):** Adding a column shouldn't take a long time to execute. + +::: + #### Grammar ```sql