Skip to content

Commit bac5dd1

Browse files
AUTO: Sync ScalarDB docs in English to docs site repo (#1049)
Co-authored-by: josh-wong <[email protected]>
1 parent 7063e4e commit bac5dd1

File tree

2 files changed

+11
-11
lines changed

2 files changed

+11
-11
lines changed

versioned_docs/version-3.14/overview.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,13 @@ This page describes what ScalarDB is and its primary use cases.
1212

1313
## What is ScalarDB?
1414

15-
ScalarDB is a hybrid transaction/analytical processing (HTAP) engine for diverse databases. It runs as middleware on databases and virtually unifies diverse databases by achieving ACID transactions and real-time analytics across them to simplify the complexity of managing multiple databases or multiple instances of a single database.
15+
ScalarDB is a universal hybrid transaction/analytical processing (HTAP) engine for diverse databases. It runs as middleware on databases and virtually unifies diverse databases by achieving ACID transactions and real-time analytics across them to simplify the complexity of managing multiple databases or multiple instances of a single database.
1616

1717
![How ScalarDB simplifies complex data management architecture.](images/scalardb.png)
1818

1919
As a versatile solution, ScalarDB supports a range of databases, including:
2020

21-
- 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.
21+
- Relational databases that support JDBC, such as MariaDB, Microsoft SQL Server, MySQL, Oracle Database, PostgreSQL, SQLite, and their compatible databases, like Amazon Aurora and YugabyteDB.
2222
- NoSQL databases like Amazon DynamoDB, Apache Cassandra, and Azure Cosmos DB.
2323

2424
For details on which databases ScalarDB supports, refer to [Databases](requirements.mdx#databases).

versioned_docs/version-3.14/schema-loader.mdx

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -532,15 +532,15 @@ Auto-scaling for Cosmos DB for NoSQL is enabled only when this option is set to
532532

533533
The following table shows the supported data types in ScalarDB and their mapping to the data types of other databases.
534534

535-
| ScalarDB | Cassandra | Cosmos DB for NoSQL | DynamoDB | MySQL | PostgreSQL/YugabyteDB | Oracle | SQL Server | SQLite |
536-
|-----------|-----------|---------------------|----------|----------|-----------------------|----------------|-----------------|---------|
537-
| BOOLEAN | boolean | boolean (JSON) | BOOL | boolean | boolean | number(1) | bit | boolean |
538-
| INT | int | number (JSON) | N | int | int | number(10) | int | int |
539-
| BIGINT | bigint | number (JSON) | N | bigint | bigint | number(19) | bigint | bigint |
540-
| FLOAT | float | number (JSON) | N | real | real | binary_float | float(24) | float |
541-
| DOUBLE | double | number (JSON) | N | double | double precision | binary_double | float | double |
542-
| TEXT | text | string (JSON) | S | longtext | text | varchar2(4000) | varchar(8000) | text |
543-
| BLOB | blob | string (JSON) | B | longblob | bytea | RAW(2000) | varbinary(8000) | blob |
535+
| ScalarDB | Cassandra | Cosmos DB for NoSQL | DynamoDB | MySQL/MariaDB | PostgreSQL/YugabyteDB | Oracle | SQL Server | SQLite |
536+
|----------|-----------|---------------------|----------|---------------|-----------------------|----------------|-----------------|---------|
537+
| BOOLEAN | boolean | boolean (JSON) | BOOL | boolean | boolean | number(1) | bit | boolean |
538+
| INT | int | number (JSON) | N | int | int | number(10) | int | int |
539+
| BIGINT | bigint | number (JSON) | N | bigint | bigint | number(16) | bigint | bigint |
540+
| FLOAT | float | number (JSON) | N | real | real | binary_float | float(24) | float |
541+
| DOUBLE | double | number (JSON) | N | double | double precision | binary_double | float | double |
542+
| TEXT | text | string (JSON) | S | longtext | text | varchar2(4000) | varchar(8000) | text |
543+
| BLOB | blob | string (JSON) | B | longblob | bytea | RAW(2000) | varbinary(8000) | blob |
544544

545545
However, the following data types in JDBC databases are converted differently when they are used as a primary key or a secondary index key. This is due to the limitations of RDB data types. For MySQL and Oracle, you can change the column size (minimum 64 bytes) as long as it meets the limitation of the total size of key columns. For details, see [Underlying storage or database configurations](configurations.mdx#underlying-storage-or-database-configurations).
546546

0 commit comments

Comments
 (0)