From 43bbffa3f9eb66c977a76a9dbb276d9eff267f25 Mon Sep 17 00:00:00 2001 From: josh-wong Date: Wed, 11 Sep 2024 10:06:40 +0000 Subject: [PATCH] AUTO: Sync ScalarDB docs in English to docs site repo --- versioned_docs/version-3.12/overview.mdx | 2 +- .../scalardb-benchmarks/README.mdx | 2 +- .../scalardb-sql/migration-guide.mdx | 4 +- .../scalardb-supported-databases.mdx | 168 ------------------ .../version-3.12/schema-loader-import.mdx | 2 +- 5 files changed, 5 insertions(+), 173 deletions(-) delete mode 100644 versioned_docs/version-3.12/scalardb-supported-databases.mdx diff --git a/versioned_docs/version-3.12/overview.mdx b/versioned_docs/version-3.12/overview.mdx index 028a5944..737c2443 100644 --- a/versioned_docs/version-3.12/overview.mdx +++ b/versioned_docs/version-3.12/overview.mdx @@ -20,7 +20,7 @@ As a versatile solution, ScalarDB supports a range of databases, including: - Relational databases that support JDBC, such as MariaDB, Microsoft SQL Server, MySQL, Oracle Database, PostgreSQL, SQLite, and their compatible databases, like Amazon Aurora, Google AlloyDB, TiDB, and YugabyteDB. - NoSQL databases like Amazon DynamoDB, Apache Cassandra, and Azure Cosmos DB. -For details on which databases ScalarDB supports, refer to [Supported Databases](scalardb-supported-databases.mdx). +For details on which databases ScalarDB supports, refer to [Databases](requirements.mdx#databases). ## Why ScalarDB? diff --git a/versioned_docs/version-3.12/scalardb-benchmarks/README.mdx b/versioned_docs/version-3.12/scalardb-benchmarks/README.mdx index 9556cb20..a03fee98 100644 --- a/versioned_docs/version-3.12/scalardb-benchmarks/README.mdx +++ b/versioned_docs/version-3.12/scalardb-benchmarks/README.mdx @@ -28,7 +28,7 @@ This tutorial describes how to run benchmarking tools for ScalarDB. Database ben - Kelpie is a framework for performing end-to-end testing, such as system benchmarking and verification. Get the latest version from [Kelpie Releases](https://github.com/scalar-labs/kelpie), and unzip the archive file. - A client to run the benchmarking tools - A target database - - For a list of databases that ScalarDB supports, see [Supported Databases](../scalardb-supported-databases.mdx). + - For a list of databases that ScalarDB supports, see [Databases](../requirements.mdx#databases). :::note diff --git a/versioned_docs/version-3.12/scalardb-sql/migration-guide.mdx b/versioned_docs/version-3.12/scalardb-sql/migration-guide.mdx index 640f3737..f0f7eebd 100644 --- a/versioned_docs/version-3.12/scalardb-sql/migration-guide.mdx +++ b/versioned_docs/version-3.12/scalardb-sql/migration-guide.mdx @@ -54,7 +54,7 @@ BM===>AM Before starting the migration, check the following questions. If the answer to any of these questions is "No", you must address them before proceeding with the migration. -- Are your target database and version one of the [supported relational databases (called JDBC databases in ScalarDB) and versions](../scalardb-supported-databases.mdx#jdbc-databases)? +- Are your target database and version one of the [supported relational databases (called JDBC databases in ScalarDB) and versions](../requirements.mdx#relational-databases)? - Do you have a fully privileged account that can manage the target database? For details, see [the general requirements](../database-configurations.mdx#general-requirements). - Do all target tables have primary keys? - Is the data type of each column supported in ScalarDB? For supported data types and how they are mapped to ScalarDB data types, see [Data-type mapping from JDBC databases to ScalarDB](../schema-loader-import.mdx#data-type-mapping-from-jdbc-databases-to-scalardb). @@ -107,7 +107,7 @@ Due to the difference in data types, ScalarDB will throw an error when writing d ## References -- [Supported Databases](../scalardb-supported-databases.mdx) +- [Supported Databases](../requirements.mdx#databases) - [ScalarDB SQL API Guide](./sql-api-guide.mdx) - [ScalarDB JDBC Guide](./jdbc-guide.mdx) - [ScalarDB SQL Grammar](./grammar.mdx) diff --git a/versioned_docs/version-3.12/scalardb-supported-databases.mdx b/versioned_docs/version-3.12/scalardb-supported-databases.mdx deleted file mode 100644 index 60ed0abf..00000000 --- a/versioned_docs/version-3.12/scalardb-supported-databases.mdx +++ /dev/null @@ -1,168 +0,0 @@ ---- -tags: - - Community - - Enterprise Standard - - Enterprise Premium ---- - -# Supported Databases - -ScalarDB supports the following databases and their versions. - -## Amazon DynamoDB - -| Version | DynamoDB | -|:------------------|:----------| -| **ScalarDB 3.13** | ✅ | -| **ScalarDB 3.12** | ✅ | -| **ScalarDB 3.11** | ✅ | -| **ScalarDB 3.10** | ✅ | -| **ScalarDB 3.9** | ✅ | -| **ScalarDB 3.8** | ✅ | -| **ScalarDB 3.7** | ✅ | - -## Apache Cassandra - -:::note - -For requirements when using Cassandra or Cassandra-compatible databases, see [How to configure databases to achieve the general requirements](requirements.mdx#how-to-configure-databases-to-achieve-the-general-requirements). - -::: - -| Version | Cassandra 4.1 | Cassandra 4.0 | Cassandra 3.11 | Cassandra 3.0 | -|:------------------|:---------------|:---------------|:----------------|:---------------| -| **ScalarDB 3.13** | ❌ | ❌ | ✅ | ✅ | -| **ScalarDB 3.12** | ❌ | ❌ | ✅ | ✅ | -| **ScalarDB 3.11** | ❌ | ❌ | ✅ | ✅ | -| **ScalarDB 3.10** | ❌ | ❌ | ✅ | ✅ | -| **ScalarDB 3.9** | ❌ | ❌ | ✅ | ✅ | -| **ScalarDB 3.8** | ❌ | ❌ | ✅ | ✅ | -| **ScalarDB 3.7** | ❌ | ❌ | ✅ | ✅ | - -## Azure Cosmos DB for NoSQL - -| Version | Cosmos DB for NoSQL | -|:------------------|:---------------------| -| **ScalarDB 3.13** | ✅ | -| **ScalarDB 3.12** | ✅ | -| **ScalarDB 3.11** | ✅ | -| **ScalarDB 3.10** | ✅ | -| **ScalarDB 3.9** | ✅ | -| **ScalarDB 3.8** | ✅ | -| **ScalarDB 3.7** | ✅ | - -## JDBC databases - -:::note - -For recommendations when using JDBC databases, see [Recommendations](requirements.mdx#recommendations). - -::: - -### Amazon Aurora MySQL - -| Version | Aurora MySQL 3 | Aurora MySQL 2 | -|:------------------|:----------------|:----------------| -| **ScalarDB 3.13** | ✅ | ✅ | -| **ScalarDB 3.12** | ✅ | ✅ | -| **ScalarDB 3.11** | ✅ | ✅ | -| **ScalarDB 3.10** | ✅ | ✅ | -| **ScalarDB 3.9** | ✅ | ✅ | -| **ScalarDB 3.8** | ✅ | ✅ | -| **ScalarDB 3.7** | ✅ | ✅ | - -### Amazon Aurora PostgreSQL - -| Version | Aurora PostgreSQL 15 | Aurora PostgreSQL 14 | Aurora PostgreSQL 13 | Aurora PostgreSQL 12 | -|:------------------|:----------------------|:----------------------|:----------------------|:----------------------| -| **ScalarDB 3.13** | ✅ | ✅ | ✅ | ✅ | -| **ScalarDB 3.12** | ✅ | ✅ | ✅ | ✅ | -| **ScalarDB 3.11** | ✅ | ✅ | ✅ | ✅ | -| **ScalarDB 3.10** | ✅ | ✅ | ✅ | ✅ | -| **ScalarDB 3.9** | ✅ | ✅ | ✅ | ✅ | -| **ScalarDB 3.8** | ✅ | ✅ | ✅ | ✅ | -| **ScalarDB 3.7** | ✅ | ✅ | ✅ | ✅ | - -### MariaDB - -| Version | MariaDB 10.11 | -|:------------------|:--------------| -| **ScalarDB 3.13** | ✅ | -| **ScalarDB 3.12** | ✅ | -| **ScalarDB 3.11** | ✅ | -| **ScalarDB 3.10** | ✅ | -| **ScalarDB 3.9** | ✅ | -| **ScalarDB 3.8** | ✅ | -| **ScalarDB 3.7** | ✅ | - -### Microsoft SQL Server - -| Version | SQL Server 2022 | SQL Server 2019 | SQL Server 2017 | -|:------------------|:-----------------|:-----------------|:-----------------| -| **ScalarDB 3.13** | ✅ | ✅ | ✅ | -| **ScalarDB 3.12** | ✅ | ✅ | ✅ | -| **ScalarDB 3.11** | ✅ | ✅ | ✅ | -| **ScalarDB 3.10** | ✅ | ✅ | ✅ | -| **ScalarDB 3.9** | ✅ | ✅ | ✅ | -| **ScalarDB 3.8** | ✅ | ✅ | ✅ | -| **ScalarDB 3.7** | ✅ | ✅ | ✅ | - -### MySQL - -| Version | MySQL 8.1 | MySQL 8.0 | MySQL 5.7 | -|:------------------|:-----------|:-----------|:-----------| -| **ScalarDB 3.13** | ✅ | ✅ | ✅ | -| **ScalarDB 3.12** | ✅ | ✅ | ✅ | -| **ScalarDB 3.11** | ✅ | ✅ | ✅ | -| **ScalarDB 3.10** | ✅ | ✅ | ✅ | -| **ScalarDB 3.9** | ✅ | ✅ | ✅ | -| **ScalarDB 3.8** | ✅ | ✅ | ✅ | -| **ScalarDB 3.7** | ✅ | ✅ | ✅ | - -### Oracle - -| Version | Oracle 23.2.0-free | Oracle 21.3.0-xe | Oracle 18.4.0-xe | -|:------------------|:--------------------|:------------------|:------------------| -| **ScalarDB 3.13** | ✅ | ✅ | ✅ | -| **ScalarDB 3.12** | ✅ | ✅ | ✅ | -| **ScalarDB 3.11** | ✅ | ✅ | ✅ | -| **ScalarDB 3.10** | ✅ | ✅ | ✅ | -| **ScalarDB 3.9** | ✅ | ✅ | ✅ | -| **ScalarDB 3.8** | ✅ | ✅ | ✅ | -| **ScalarDB 3.7** | ✅ | ✅ | ✅ | - -### PostgreSQL - -| Version | PostgreSQL 15 | PostgreSQL 14 | PostgreSQL 13 | PostgreSQL 12 | -|:------------------|:---------------|:---------------|:---------------|:---------------| -| **ScalarDB 3.13** | ✅ | ✅ | ✅ | ✅ | -| **ScalarDB 3.12** | ✅ | ✅ | ✅ | ✅ | -| **ScalarDB 3.11** | ✅ | ✅ | ✅ | ✅ | -| **ScalarDB 3.10** | ✅ | ✅ | ✅ | ✅ | -| **ScalarDB 3.9** | ✅ | ✅ | ✅ | ✅ | -| **ScalarDB 3.8** | ✅ | ✅ | ✅ | ✅ | -| **ScalarDB 3.7** | ✅ | ✅ | ✅ | ✅ | - -### SQLite - -| Version | SQLite 3 | -|:------------------|:----------| -| **ScalarDB 3.13** | ✅ | -| **ScalarDB 3.12** | ✅ | -| **ScalarDB 3.11** | ✅ | -| **ScalarDB 3.10** | ✅ | -| **ScalarDB 3.9** | ✅ | -| **ScalarDB 3.8** | ❌ | -| **ScalarDB 3.7** | ❌ | - -### YugabyteDB - -| Version | YugabyteDB 2 | -|:------------------|:-------------| -| **ScalarDB 3.13** | ✅ | -| **ScalarDB 3.12** | ❌ | -| **ScalarDB 3.11** | ❌ | -| **ScalarDB 3.10** | ❌ | -| **ScalarDB 3.9** | ❌ | -| **ScalarDB 3.8** | ❌ | -| **ScalarDB 3.7** | ❌ | diff --git a/versioned_docs/version-3.12/schema-loader-import.mdx b/versioned_docs/version-3.12/schema-loader-import.mdx index 45df04d3..23b16d15 100644 --- a/versioned_docs/version-3.12/schema-loader-import.mdx +++ b/versioned_docs/version-3.12/schema-loader-import.mdx @@ -33,7 +33,7 @@ This tool only changes database metadata. Thus, the processing time does not inc ### Requirements -- [JDBC databases](./scalardb-supported-databases.mdx#jdbc-databases), except for SQLite, can be imported. +- [JDBC databases](./requirements.mdx#relational-databases), except for SQLite, can be imported. - Each table must have primary key columns. (Composite primary keys can be available.) - Target tables must only have columns with supported data types. For details, see [Data-type mapping from JDBC databases to ScalarDB](#data-type-mapping-from-jdbc-databases-to-scalardb)).