Skip to content
Merged
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
28 changes: 15 additions & 13 deletions docs/schema-loader.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -532,19 +532,19 @@ Auto-scaling for Cosmos DB for NoSQL is enabled only when this option is set to

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

| ScalarDB | Cassandra | Cosmos DB for NoSQL | Db2 | DynamoDB | MySQL/MariaDB/TiDB | PostgreSQL/YugabyteDB/AlloyDB | Oracle | SQL Server | SQLite |
|-------------|----------------------|---------------------|----------------|----------|--------------------|-------------------------------|--------------------------|-----------------|---------|
| BOOLEAN | boolean | boolean (JSON) | BOOLEAN | BOOL | boolean | boolean | number(1) | bit | boolean |
| INT | int | number (JSON) | INT | N | int | int | number(10) | int | int |
| BIGINT | bigint | number (JSON) | BIGINT | N | bigint | bigint | number(16) | bigint | bigint |
| FLOAT | float | number (JSON) | REAL | N | real | real | binary_float | float(24) | float |
| DOUBLE | double | number (JSON) | DOUBLE | N | double | double precision | binary_double | float | double |
| TEXT | text | string (JSON) | VARCHAR(32672) | S | longtext | text | varchar2(4000) | varchar(8000) | text |
| BLOB | blob | string (JSON) | BLOB(2G) | B | longblob | bytea | BLOB | varbinary(8000) | blob |
| DATE | date | number (JSON) | DATE | N | date | date | date | date | int |
| TIME | time | number (JSON) | TIMESTAMP | N | time | time | timestamp | time | bigint |
| TIMESTAMP | <em>Unsupported</em> | number (JSON) | TIMESTAMP | N | datetime | timestamp | timestamp | datetime2 | bigint |
| TIMESTAMPTZ | timestamp | number (JSON) | TIMESTAMP | N | datetime | timestamp with time zone | timestamp with time zone | datetimeoffset | bigint |
| ScalarDB | Cassandra | Cosmos DB for NoSQL | Db2 | DynamoDB | MySQL/MariaDB/TiDB | PostgreSQL/YugabyteDB/AlloyDB | Oracle | SQL Server | SQLite | Object Storage |
|-------------|----------------------|---------------------|----------------|----------|--------------------|-------------------------------|--------------------------|-----------------|---------|----------------|
| BOOLEAN | boolean | boolean (JSON) | BOOLEAN | BOOL | boolean | boolean | number(1) | bit | boolean | boolean (JSON) |
| INT | int | number (JSON) | INT | N | int | int | number(10) | int | int | number (JSON) |
| BIGINT | bigint | number (JSON) | BIGINT | N | bigint | bigint | number(16) | bigint | bigint | number (JSON) |
| FLOAT | float | number (JSON) | REAL | N | real | real | binary_float | float(24) | float | number (JSON) |
| DOUBLE | double | number (JSON) | DOUBLE | N | double | double precision | binary_double | float | double | number (JSON) |
| TEXT | text | string (JSON) | VARCHAR(32672) | S | longtext | text | varchar2(4000) | varchar(8000) | text | string (JSON) |
| BLOB | blob | string (JSON) | BLOB(2G) | B | longblob | bytea | BLOB | varbinary(8000) | blob | string (JSON) |
| DATE | date | number (JSON) | DATE | N | date | date | date | date | int | number (JSON) |
| TIME | time | number (JSON) | TIMESTAMP | N | time | time | timestamp | time | bigint | number (JSON) |
| TIMESTAMP | <em>Unsupported</em> | number (JSON) | TIMESTAMP | N | datetime | timestamp | timestamp | datetime2 | bigint | number (JSON) |
| TIMESTAMPTZ | timestamp | number (JSON) | TIMESTAMP | N | datetime | timestamp with time zone | timestamp with time zone | datetimeoffset | bigint | number (JSON) |

:::note

Expand Down Expand Up @@ -579,6 +579,8 @@ Oracle BLOB type cannot be used as a partition key, clustering key, secondary in

YugabyteDB has limitations that prevent floating point types (FLOAT and DOUBLE) from functioning correctly as a primary key, clustering keys, or secondary index keys.

With Object Storage, BLOB-type data larger than 1.5 GiB cannot be stored.

## Internal transaction metadata for Consensus Commit

The Consensus Commit transaction manager manages transaction metadata (for example, transaction ID, record version, and transaction status) stored along with the actual records to handle transactions properly.
Expand Down