Skip to content

Data Type Support Overview

  • ✅ : Supported
  • ❌ : Unsupported. The driver cannot process this type; reading it will cause an error.
  • 🔢 : As Number. Handled as a numeric value.
  • 🔤 : As String. Handled as a text string.
  • 🅱️ : As Bytes. Handled as a Base64 encoded string.
  • 0️⃣1️⃣ : As Bitstring. Handled as a string of 0s and 1s.
  • - : Depends. Based on user/driver behavior.

ClickHouse

NOTE

ClickHouse updates are heavyweight, asynchronous mutations. Therefore, direct row editing is not supported in the UI.

TypeRead/Show/ExportImport
Int8
Int16
Int32
Int64
Int128
Int256
UInt8
UInt16
UInt32
UInt64
UInt128
UInt256
Float32
Float64
BFloat16
Decimal
Decimal32
Decimal64
Decimal128
Decimal256
String
FixedString
Date
Date32
Time🔢
DateTime
Time64
DateTime64
Enum🔤
UUID🔤
JSON
IPV4🔤
IPV6🔤
Array🔤
Bool
Tuple🔤
Map🔤
Variant🔤
Point🔤
Ring🔤
LineString🔤
MultiLineString🔤
Polygon🔤
MultiPolygon🔤

DuckDB

TypeRead/Show/ExportEditImport
BIGINT
BLOB
BOOLEAN
DATE
DECIMAL--
DOUBLE
FLOAT
HUGEINT
INTEGER
BIGNUM
UHUGEINT
JSON
SMALLINT
TIME
TIMESTAMP
TINYINT
UBIGINT
UINTEGER
USMALLINT
UTINYINT
UUID🔤🔤
VARCHAR
ARRAY🔤--
LIST🔤--
MAP🔤--
STRUCT🔤--
UNION🔤--
INTERVAL🔤🔤
BIT

NOTE

  • DECIMAL : Treated as Float64 for editing or importing.
  • BIT: These are not supported by the driver; attempting to read them will result in an error.
  • ARRAY/LIST/MAP/STRUCT/UNION: These nested types are fully supported. They are handled as JSON strings for both display and driver submission.

IBM DB2

TypeRead/Show/ExportEditImport
SMALLINT
INTEGER
BIGINT
FLOAT
DECIMAL
CHAR
VARCHAR
CLOB
BINARY
VARBINARY
BLOB
DATE
TIME
TIMESTAMP
XML🔤🔤
GRAPHIC---
VARGRAPHIC---
DBCLOB---

NOTE

DBCLOB and GRAPHIC types use UTF-16 encoding, which may cause error 01517 or driver crashes during data retrieval. In custom queries, use CAST(column_name AS CLOB) to convert these columns into a compatible format.

MsSQL

TypeRead/Show/ExportEditImport
tinyint
smallint
int
bitboolbool
decimal
numeric
money
smallmoney
float
real
date
time
datetime2
datetimeoffset
datetime
smalldatetime
char
varchar
text
binary
varbinary
image
geography🅱️🅱️
geometry🅱️🅱️
hierarchyid🅱️🅱️
json
uniqueidentifier🔤🔤
xml🔤🔤

MySQL

TypeRead/Show/ExportEditImport
BIT🅱️🅱️
TINYINT
BOOL🔢🔢
SMALLINT
MEDIUMINT
INT
BIGINT
DECIMAL
FLOAT
DOUBLE
DATE
TIME🔤
DATETIME
TIMESTAMP
YEAR🔢🔢
CHAR
VARCHAR
BINARY
VARBINARY
BLOB
TEXT
ENUM🔤🔤
SET🔤🔤
GEOMETRY🅱️🅱️
POINT🅱️🅱️
LINESTRING🅱️🅱️
POLYGON🅱️🅱️
MULTIPOINT🅱️🅱️
MULTILINESTRING🅱️🅱️
MULTIPOLYGON🅱️🅱️
GEOMETRYCOLLECTION🅱️🅱️
JSON

Oracle DB

TypeRead/Show/ExportEditImport
CHAR
NCHAR
VARCHAR2
NVARCHAR2
NUMBER
FLOAT
BINARY_FLOAT
BINARY_DOUBLE
CLOB
NCLOB
BLOB
DATE
TIMESTAMP
INTERVAL🔤🔤🔤
LONG RAW
JSON
BOOLEAN🔢🔢🔢
*VECTOR🔤🔤🔤
XMLTYPE🔤🔤🔤
OBJECT🔤--

NOTE

  • Oracle Object Types are converted to JSON strings upon retrieval. For Edit and Import, the input is also treated as a JSON string. DBNova resolves the ObjectType based on the column type and invokes ObjectType#FromJSON to convert the string back into an object.
  • Limitation: The driver's FromJSON implementation is currently incomplete. Based on my tests, it only supports simple structures (e.g., HTMLURITYPE), while complex types like SDO_GEOMETRY will trigger errors. This appears to be a common issue across various language drivers (likely an upstream limitation in ODPI-C).
  • Workaround: If needed, use Raw SQL to perform edits on complex Object Types.

NOTE

On macOS, DBNova is provided as an x86_64 binary. Since the latest Oracle Instant Client version for x86_64 is 19.16, behaviors may vary from the table shown above.

PostgresQL

TypeRead/Show/ExportEditImport
bigint
bigserial
bit0️⃣1️⃣0️⃣1️⃣
bit varying0️⃣1️⃣0️⃣1️⃣
boolean
box🔤🔤
bytea
character
character varying
cidr🔤🔤
circle🔤🔤
date
double precision
inet🔤🔤
integer
interval🔤🔤
json
jsonb
line🔤🔤
lseg🔤🔤
macaddr🔤🔤
macaddr8🔤🔤
money🔤🔤
numeric
path🔤🔤
point🔤🔤
polygon🔤🔤
real
smallint
smallserial
serial
text
time
timestamp
tsquery🔤🔤
tsvector🔤🔤
uuid🔤🔤
xml🔤🔤
* array🔤🔤
hstore🔤🔤
* range🔤🔤

SQLite

SQLite has only four data types, and all are supported.