|
<< Click to Display Table of Contents >> Data Type Support |
Overview
When setting Replication or Virtualization through the Wizard (that is, when using the default components and Classes for Replication or Virtualization provided by Bizagi), Bizagi will support the mapping of attributes to a comprehensive set of supported data types.
The following information lists the supported data types when using Bizagi's native integration to external SQL Server or Oracle databases.
The tables below shows the column mappings from the data source to Bizagi when using Replication or Virtualization. The first column displays the source data types, and the second column presents the equivalent data type in Bizagi, if supported.
SQL Server data types |
|
|---|---|
Character Strings |
|
CHAR |
String |
VARCHAR |
String |
TEXT / VARCHAR(MAX) |
Not supported |
Exact Numbers |
|
BIGINT |
Big Integer |
INT |
Integer |
SMALLINT |
Small Integer |
TINYINT |
Tiny Integer |
DECIMAL |
Currency |
NUMERIC |
Integer If the number is too big, after the Replication or Virtualization configuration, it has to be changed manually to Big Integer. |
MONEY |
Currency |
SMALLMONEY |
Currency (limited support) |
BIT |
Boolean |
Approximate Numbers |
|
FLOAT |
Float |
REAL |
Real |
Date and Time |
|
DATE |
Date-time |
DATETIME |
Date-time |
SMALLDATETIME |
Not supported |
Binary strings |
|
BINARY |
Not supported |
VARBINARY |
Not supported |
IMAGE |
Not supported |
Unicode Character Strings |
|
NCHAR |
String |
NVARCHAR |
String |
NTEXT |
Not supported |
Other Data Types |
|
UNIQUEIDENTIFIER |
Not supported |
TIMESTAMP |
Not supported |
CURSOR |
Not supported |
SQL_VARIANT |
Not supported |
TABLE |
Not supported |
XML |
Not supported |
Oracle data types |
|
|---|---|
Character Data types |
|
CHAR |
String (limited support) |
NCHAR |
String (limited support) |
NVARCHAR |
String (limited support) |
VARCHAR |
String Oracle recommends to use varchar2 instead. |
VARCHAR2 |
String |
LONG |
Not supported |
RAW |
Not supported |
LONG RAW |
Not supported |
Numeric Data types |
|
NUMBER(1) |
Tiny Integer |
NUMBER (3) |
Tiny Integer |
NUMBER (6) |
Small Integer |
NUMBER(10) |
Integer |
NUMBER (19) |
Big Integer |
NUMBER (17,4) |
Float |
NUMBER(18,4) |
Float |
NUMBER (19,4) |
Float |
NUMBER |
Oracle Number (available only when using Oracle as the repository of Bizagi)*. |
NUMBER (20) |
Oracle Number (available only when using Oracle as the repository of Bizagi)*. |
NUMBER (38) |
Oracle Number (available only when using Oracle as the repository of Bizagi)*. |
NUMERIC |
Big Integer |
FLOAT |
Float |
DEC |
Big Integer |
DECIMAL |
Big Integer |
Date/Time Data types |
|
DATE |
Date-time |
TIMESTAMP |
Not supported |
INTERVAL YEAR |
Not supported |
INTERVAL DAY |
Not supported |
Large Object (LOB) Data types |
|
BFILE |
Not supported |
BLOB |
Not supported |
CLOB |
Not supported |
NCLOB |
Not supported |
Rowid Data types |
|
ROWID |
Not supported |
UROWID |
Not supported |
XML Data types |
|
XMLTYPE |
Not supported |
For CHAR, NCHAR, and NVARCHAR, it is not supported its use in primary keys (Oracle itself does not promote this as a good practice).
*Oracle number data type cannot be used in Business rules, within any XPath functions. It cannot be used as Vocabulary in Policies, in Database Encryption, nor as a Business Key.
Important
When using data virtualization or data replication, consider that you should guarantee the same (or at least very similar) collations (for SQL Server) or character sets (for Oracle), between the external database and Bizagi's database.
This is critical if the data you will be synchronizing (mainly for string data types), contain information which has a strong dependency on such configuration.
For example, if you are integrating an external Oracle database using Unicode, make sure you are using an Oracle Unicode database as well for your Bizagi project.