Data types

 

IMPORT/EXPORT WITH MySQL OR MariaDB

vp7_en_datatype_mysql_1
vp7_en_datatype_mysql_2

(*) Persistent headings only

(**) For export only

MySQL Data Types not included:

SMALLINT, TINYINT, MEDIUMINT, BIGINT, FLOAT, DOUBLE, BIT, CHAR, TINYTEXT, LONGTEXT, BLOB, DATE, TIME, TIMESTAMP

IMPORT/EXPORT WITH SQLSERVER

vp7_en_datatype_sqlserver_1
vp7_en_datatype_sqlserver_2

(*) Persistent headings only

(**) For export only

SQLServer Data Types not included:

BIGINT, SMALLINT, TINYINT, DATE, DATETIME2, DATETIMEOFFSET, SMALLDATETIME, TIME, TIMESTAMP, NTEXT, GEOGRAPHY, GEOMETRY, HIERARCHYID, SMALLMONEY, SQL_VARIANT, UNIQUEIDENTIFIER, BINARY, VARBINARY, XML

IMPORT/EXPORT WITH ORACLE

vp7_en_datatype_oracle_1
vp7_en_datatype_oracle_2

(*) Persistent headings only

(**) For export only

ORACLE Data Types not included:

CHAR, NCHAR, NVARCHAR2, LONG, LONGRAW, RAW, ROWID, UROWID, NCBLOB, BFILE, TIMESTAMP, INTERVAL YEAR, INTERVAL DAY, BINARY DOUBLE, BINARY FLOAT, XMLTYPE

NOTES

 

Columns not permitted to be left blank

 

The creation of a record in a table of the database must set a value for those columns not permitted to be left blank, and for which there is no defined default value.

This is always true, therefore also in the event of a record created by an export from VISUAL PLANNING.

If these columns have no default value, the export must provide a value (choice of characteristic in the definition of the context) and each entity exported must actually have a value for the chosen characteristics. Otherwise, when exporting, you will get:

export_incorrect

Format not accepted

When defining an export context, if the columns in the chosen table are of a format not accepted by VISUAL PLANNING, a message is added to the server log.

E.g.: 2012-10-09 12:31:00.821 WARNING MySQLConnection.getTables (line 330): Unknown columnname=exchange._tinyint type=TINYINT size=3

Character string

The data provided for import, in the form of a character string, must respect the format expected by the database (Date, Time, Number, etc.).

 

Format incompatible

The importation of data of a format not compatible with the destination, in VISUAL PLANNING, will lead to the addition of a message in the Server Log.

For example: 2012-10-09 14:24:59.290 SEVERE HeadingType.setValue (line 210): Bad format for heading’Integer’: varchar

Tips for data imports

The importation of data exported from Visual Planning is operational. Do not hesitate in using it to discover the data formats when using a Text-type column.

Print Friendly, PDF & Email
1 Etoile2 Etoiles3 Etoiles4 Etoiles5 Etoiles (3 votes, average : 5.00 on 5)
Loading...
Consulting training

Need training?

Use our consulting services!