Data Type Mapping
Datalogger data types are mapped into database data types differently depending on the type of database as described below.
SQL Server Compact
Datalogger Data Type |
SQL Server Compact Data Type |
Notes |
IEEE8 |
FLOAT |
|
IEEE4 |
REAL |
|
FP2 |
REAL |
|
Long |
INT |
|
UINT2 |
INT |
|
String |
NVARCHAR(2048) |
|
Boolean |
BIT |
|
Bool8 |
BIT |
|
Nsec |
DATETIME |
Resolution is 3ms |
SQL Server
Datalogger Data Type |
SQL Server |
Notes |
IEEE8 |
FLOAT(53) |
|
IEEE4 |
REAL |
|
FP2 |
REAL |
|
Long |
INT |
|
UINT2 |
INT |
|
String |
NVARCHAR(MAX) |
|
Boolean |
BIT |
|
Bool8 |
BIT |
|
Nsec |
DATETIME or DATETIME2 |
Record Timestamp is DateTime2 (resolution is 100ns). All others are DateTime (resolution is 3ms). |
MySQL
Datalogger Data Type |
MySQL |
Notes |
IEEE8 |
DOUBLE |
|
IEEE4 |
FLOAT |
MySQL FLOAT data type only stores 6 digits of precision. The datalogger stores 7. |
FP2 |
FLOAT |
|
Long |
INT |
|
UINT2 |
SMALLINT UNSIGNED |
|
String |
TEXT |
|
Boolean |
BIT(1) |
|
Bool8 |
BIT(1) |
|
Nsec |
DATETIME |
MySQL DATETIME does not support subsecond information. |
Oracle
Datalogger Data Type |
Oracle |
Notes |
IEEE8 |
BINARY_DOUBLE |
|
IEEE4 |
BINARY_FLOAT |
|
FP2 |
BINARY_FLOAT |
|
Long |
Number(10,0) |
|
UINT2 |
Number(5,0) |
|
String |
NVARCHAR2(2000) |
|
Boolean |
Number(1,0) |
|
Bool8 |
Number(1,0) |
|
Nsec |
TIMESTAMP |
Resolution is 1 microsecond |
PostgreSQL
Datalogger Data Type |
PostgreSQL |
Notes |
IEEE8 |
double precision |
|
IEEE4 |
real |
|
FP2 |
real |
|
Long |
integer |
|
UINT2 |
integer |
|
String |
text |
|
Boolean |
boolean |
|
Bool8 |
boolean |
|
Nsec |
timestamp |
Resolution is 1 microsecond |