Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion versioned_docs/version-3.12/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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?

Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-3.12/scalardb-benchmarks/README.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
4 changes: 2 additions & 2 deletions versioned_docs/version-3.12/scalardb-sql/migration-guide.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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).
Expand Down Expand Up @@ -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)
Expand Down
168 changes: 0 additions & 168 deletions versioned_docs/version-3.12/scalardb-supported-databases.mdx

This file was deleted.

2 changes: 1 addition & 1 deletion versioned_docs/version-3.12/schema-loader-import.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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)).

Expand Down
Loading