Skip to main content
The supported client-side SQLite types are:
  1. null
  2. integer: a 64-bit signed integer
  3. real: a 64-bit floating point number
  4. text: A UTF-8 text string
  5. blob: Binary data

​
Postgres Type Mapping

Postgres types are mapped to SQLite types as follows:
Postgres Data TypePowerSync / SQLite Column TypeNotes
text, varchartext
int2, int4, int8integer
numeric / decimaltextThese types have arbitrary precision in Postgres, so can only be represented accurately as text in SQLite
boolinteger1 for true, 0 for false. There is no dedicated boolean data type in SQLite.
float4, float8real
enumtext
uuidtext
timestamptztextFormat: YYYY-MM-DD hh:mm:ss.sssZ. This is compatible with ISO8601 and SQLite’s functions. Precision matches the precision used in Postgres. -infinity becomes 0000-01-01 00:00:00Z and infinity becomes 9999-12-31 23:59:59Z.
timestamptextFormat: YYYY-MM-DD hh:mm:ss.sss. In most cases, timestamptz should be used instead. -infinity becomes 0000-01-01 00:00:00 and infinity becomes 9999-12-31 23:59:59.
date, timetext
json, jsonbtextjson and jsonb values are treated as text values in their serialized representation. JSON functions and operators operate directly on these text values.
intervaltext
macaddrtext
inettext
byteablobCannot sync directly to client — convert to hex or base64 first. See Operators & Functions.
geometry (PostGIS)textHex string of the binary data. Use the ST functions to convert to other formats
ArraystextJSON array.
DOMAIN typestext / dependsDepending on compatibility options, inner type or raw wire representation (legacy).
Custom typestextDepending on compatibility options, JSON object or raw wire representation (legacy).
(Multi-)rangestextDepending on compatibility options, JSON object (array for multi-ranges) or raw wire representation (legacy).
Binary data can be accessed in the Sync Streams / Sync Rules, but cannot be used as parameters. To sync binary columns/fields to clients, those columns need to be converted to hex or base64 representation using the relevant functions.

​
MongoDB Type Mapping

MongoDB types are mapped to SQLite types as follows:
BSON TypePowerSync / SQLite Column TypeNotes
Stringtext
Int, Longinteger
Doublereal
Decimal128text
ObjecttextConverted to a JSON string
ArraytextConverted to a JSON string
ObjectIdtextLower-case hex string
UUIDtextLower-case hex string
Booleaninteger1 for true, 0 for false. There is no dedicated boolean data type in SQLite.
DatetextFormat: YYYY-MM-DD hh:mm:ss.sssZ
Nullnull
BinaryblobCannot sync directly to client — convert to hex or base64 first. See Operators & Functions.
Regular ExpressiontextJSON text in the format {"pattern":"...","options":"..."}
TimestampintegerConverted to a 64-bit integer
Undefinednull
DBPointertextJSON text in the format {"collection":"...","oid":"...","db":"...","fields":...}
JavaScripttextJSON text in the format {"code": "...", "scope": ...}
Symboltext
MinKey, MaxKeynull
  • Data is converted to a flat list of columns, one column per top-level field in the MongoDB document.
  • Special BSON types are converted to plain SQLite alternatives. For example, ObjectId, Date, UUID are all converted to a plain TEXT column.
  • Nested objects and arrays are converted to JSON, and JSON functions and operators can be used to query them (in the Sync Streams / Sync Rules and/or on the client-side SQLite statements).
  • Binary data nested in objects or arrays is not supported.
Binary data can be accessed in the Sync Streams / Sync Rules, but cannot be used as parameters. To sync binary columns/fields to clients, those columns need to be converted to hex or base64 representation using the relevant functions.

​
MySQL Type Mapping

MySQL support is currently in a Beta release.
MySQL types are mapped to SQLite types as follows:
MySQL Data TypePowerSync / SQLite Column TypeNotes
tinyint, smallint, mediumint, bigint, integer, intinteger
numeric, decimaltext
bool, booleaninteger1 for true, 0 for false. There is no dedicated boolean data type in SQLite.
float, double, realreal
enumtext
settextConverted to JSON array
char, varchartext
tinytext, text, mediumtext, longtexttext
timestamptextISO 8601 format: YYYY-MM-DDTHH:mm:ss.sssZ
datetextFormat: YYYY-MM-DD
time, datetimetextISO 8601 format: YYYY-MM-DDTHH:mm:ss.sssZ
yeartext
jsontextThere is no dedicated JSON type in SQLite — JSON functions operate directly on text values.
bitblob* See note below regarding syncing binary types
binary, varbinaryblob
imageblob
geometry, geometrycollectionblob
point, multipointblob
linestring, multilinestringblob
polygon, multipolygonblob
Binary data can be accessed in the Sync Streams / Sync Rules, but cannot be used as parameters. To sync binary columns/fields to clients, those columns need to be converted to hex or base64 representation using the relevant functions.

​
SQL Server Type Mapping

SQL Server support is currently in a Beta release.
SQL Server types are mapped to SQLite types as follows:
SQL Server Data TypePowerSync / SQLite Column TypeNotes
tinyint, smallint, int, bigintinteger
numeric, decimaltextNumeric string
float, realreal
bitinteger
money, smallmoneytextNumeric string
xmltext
char, nchar, ntexttext
varchar, nvarchar, texttext
uniqueidentifiertext
timestamptextISO 8601 format: YYYY-MM-DDTHH:mm:ss.sssZ
datetextFormat: YYYY-MM-DD
timetextFormat: HH:mm:ss.sss
datetime, datetime2, smalldatetime, datetimeoffsettextISO 8601 format: YYYY-MM-DDTHH:mm:ss.sssZ
jsontextOnly exists for Azure SQL Database and SQL Server 2025
geometry, geographytexttext of JSON object describing the spatial data type
binary, varbinary, imageblob* See note below regarding binary types
rowversion, timestampblob* See note below regarding binary types
User Defined Types: hiearchyidblob* See note below regarding binary types
Binary data can be accessed in the Sync Streams / Sync Rules, but cannot be used as parameters. To sync binary columns/fields to clients, those columns need to be converted to hex or base64 representation using the relevant functions.