DocumentationAPI Reference
Documentation

Data Types

Using supported data types

Source tables may be synced to a number of different destination databases or data warehouses. While many databases represent most data types the same, there are a number of differences across naming conventions. Therefore, as part of the Prequel configuration, each destination column must be manually typed with one of the PREQUEL types below so that the table can be per destination with the right data type.

📘

Using the following PREQUEL type maps

The PREQUEL type used during configuration is used for two purposes:

  • Specifying the source type during source and data model configuration. To determine the right PREQUEL type to write in your config, use the "Source type mapping" table.
  • Predicting the destination type based on the connected destination. To predict the data type that will be loaded into a given destination, use the "Destination type mapping".

Source type mapping

If you are configuring your source and need to decide what PREQUEL type to use, reference this table.

Prequel TypeSupportedAthenaBigQueryClickhouseDatabricksMySQLPostgresRedshiftSnowflakeSQL Server
bytes✔️binarybytesblob, mediumblob, longblobbinarybinary, varbinary, blob, mediumblob, longblobbyteaVARBYTE, VARBINARY, BINARY VARYINGbinary, varbinarybinary, image, varbinary
string✔️char, varchar, stringstringstring, fixedstring, text, mediumtext, longtext, varcharstringstring, char, text, longtext, varcharchar, character, character varying, text, uuid, varcharCHAR, CHARACTER, NCHAR, BPCHAR, CHARACTER VARYING, NVARCHAR, TEXTCHAR, CHARACTER, NCHAR, BPCHAR, CHARACTER VARYING, NVARCHAR, TEXTchar, varchar, text, nvarchar, ntext, nchar
boolean✔️booleanboolbool, booleanbooleanbooleanbooleanbooleanbooleanbit
integer✔️smallint, integersmallint, int64, bigintint, int8, int16, int32smallint, intsmallint, mediumint, intsmallint, integersmallint, integersmallint, integersmallint, int
bigint✔️bigintint64, bigintint64, bigintbigintbigintbigintbigintbigintbigint
decimal✔️decimaldecimal, numericdecimal, numericdecimal, dec, numericdecimal, numericdecimal, numericdecimal, numericdecimal, numericdecimal, numeric
float✔️real, floatfloat64float32, float64, doublefloat, doublefloat, doublereal, double precisionreal, float4, float8, double precisionreal, float4, float8, double precisionfloat, real
timestamp✔️timestamptimestampdatetime, Datetime64timestamptimestamp, datetimetimestamp, timestamptztimestamp, timestamptztimestamp, timestamp_ntz, timestamp_tz, timestamp_ltzdatetime2
date✔️datedatedatedatedatedatedatedatedate
json✔️varchar, stringjsonstring*stringjsonjson, jsonbvarchar(MAX)varchar, variantnvarchar(MAX)
time*✖️varchar, stringtimetimestringtimetimetimetimetime

* An asterisk indicates partial support. Ask us about any specific data type limitations.

Destination type mapping

If you are predicting what data type your destination will receive, reference this table.

Prequel TypeSupportedAthenaBigQueryClickhouseDatabricksMySQLPostgresRedshiftSnowflakeSQL Server
bytes✔️stringbytesblobbinarybinarybyteaVARBYTE(MAX)*binaryblob
string✔️stringstringstringstringtexttextvarchar(MAX)textnvarchar(MAX)
boolean✔️booleanboolbooleanbooleanbooleanbooleanbooleanbooleanbit
integer✔️integerint64integerintintintegerbigintintegerint
bigint✔️bigintbigintbigintbigintbigintbigintbigintbigintbigint
decimal✔️decimaldecimaldecimaldecimaldecimaldecimaldecimaldecimaldecimal
float✔️floatfloat64doubledoubledoubledouble precisiondouble precisionfloat
timestamp✔️timestamptimestampDatetime64timestamptimestamptimestamptztimestamptztimestamp_tzdatetime2
date✔️datedatedatedatedatedatedatedatedate
json✔️stringjson*string*stringjsonjsonbvarchar(MAX)variantnvarchar(MAX)

* An asterisk indicates partial or incomplete support. Ask us about any specific data type limitations.