# Understanding Data Typing

The data types Stitch supports for replication fall into two categories:

* **Common**, which are data types supported for all integrations.

  **Note**: If a data type isn’t present in the **Common data type** list, it means that Stitch doesn’t currently support replication for that data type. [Replicating columns with unsupported data types may lead to issues with replication](https://help.qlik.com/en-US/stitch/replication/data-typing#sync-unsupported-data-types).

* **Integration-specific**, which are data types applicable only to specific integrations. For the sake of transparency, integration specific lists contain both supported and unsupported data types. Icons in the list indicate whether the data type is supported by Stitch.

* Common data types
* Integration-specific data types

As of **June 19, 2018**, the data types in the table below are supported for all integrations.

| BIGINT | BIT | CHAR | DATE |
| --- | --- | --- | --- |
| DECIMAL | DOUBLE | FLOAT | INTEGER |
| LONGVARCHAR | LONGNVARCHAR | NCHAR | NVARCHAR |
| NUMERIC | REAL | SMALLINT | TIME |
| TIMESTAMP | [TINYINT](https://help.qlik.com/en-US/stitch/troubleshooting/mysql-tinyint1-stored-as-bit)<br><br>the Info icon<br><br>Under certain circumstances, Stitch may store this data type as `BIT(1)/boolean`. Click the link for more details. | VARCHAR |  |

The integrations listed below also have data types that are specific to them. Click the links for more info, including the level of support Stitch offers and the Stitch data type it will map to.

* [Amazon Aurora MySQL RDS](https://help.qlik.com/en-US/stitch/integrations/databases/amazon-aurora-mysql#data-types)
* [Amazon Oracle RDS](https://help.qlik.com/en-US/stitch/integrations/databases/amazon-oracle-rds#data-types)
* [Google CloudSQL MySQL](https://help.qlik.com/en-US/stitch/integrations/databases/google-cloudsql-mysql#data-types)
* [MariaDB](https://help.qlik.com/en-US/stitch/integrations/databases/mariadb#data-types)
* [Microsoft SQL Server](https://help.qlik.com/en-US/stitch/integrations/databases/microsoft-sql-server#data-types)
* [MySQL](https://help.qlik.com/en-US/stitch/integrations/databases/mysql#data-types)
* [Oracle](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#data-types)
* [PostgreSQL](https://help.qlik.com/en-US/stitch/integrations/databases/postgresql#data-types)

## Columns with mixed data types

Occasionally Stitch will encounter a column that contains more than one data type. As Stitch requires that there be only one data type per column to properly type and store your data, columns containing multiple data types may be “split” to ensure all values are correctly typed.

For example: an `order_confirmed` column is synced and typed as `BOOLEAN`. In a subsequent sync, Stitch detects `VARCHAR` values in this column.

As a result, Stitch will create an additional column to accommodate the `VARCHAR` values. The new column name will be the original name appended with the data type: `order_confirmed__string`

How columns are named depends on the type of destination being used to warehouse data. Refer to the [Mixed Data Types guide for more info](https://help.qlik.com/en-US/stitch/replication/loading/understanding-table-structural-changes#columns-mixed-data-types).

## Replicating unsupported data types

Columns containing data types that aren’t supported may prevent an entire table from replicating.

If you determine a non-replicating column contains an unsupported data type, you’ll need to de-select it to allow the table to successfully replicate.

## ‘Not Supported’ status for columns

If a column you want to sync has a Status of `Not Supported`, the root cause may be an [unsupported data type or insufficient user permissions](https://help.qlik.com/en-US/stitch/troubleshooting/non-replicating-data-unsupported-data-types).