search

sfa-siard / SiardGui

SIARD Suite - SiardGui
Other
17 stars 3 forks source link

ORACLE-->SIARD: Datum: positions after decimal point are deleted if all values are 0 #43

Open ibbenz opened 2 years ago

ibbenz commented 2 years ago

A SIARD-file is uploaded in an Oracle DB. Afterwards the uploaded data is downloaded from the Oracle DB back into a new SIARD-file. During the download-process data changes. In case of only-0 after the decimal point, the Datum is truncated. However this datachange is the reason for a validation-error in the dbptk-validation tool for siard files. Therefore I would like to know, if the truncation is conform with siard 2.1 and the dbptk-tool is wrong or if the dbptk-tool detects correctly the truncation as an error.

The Datum in the original SIARD-file: 1992-05-01T00:00:00.000000000
The Datum in the SIARD created by download data from the Oracle DB: 1992-05-01T00:00:00Z

Due to this change in the Datum the following error is issued in the dbptk-siard-Validator: Data type invalid - 1992-05-01T00:00:00Z is not in conformity with 'TIMESTAMP' type in content/schema0/table2/table2.xml

The TIMESTAMP-type in the .xsd is the type dateType which is defined as follows:

SIARD-file: [0_1-3_Northwind_simple_220913_B.zip](https://github.com/sfa-siard/SiardGui/files/9616202/0_1-3_Northwind_simple_220913_B.zip)
walkerjan commented 2 years ago

Thanks a lot for reporting this issue.

We shall have a look at it and get back to you as soon as possible.

ibbenz commented 2 years ago

The same error occurs in case of a postgreSQL-Database. The following process was executed:

Import of SIARD in postgreSQL: 0_1-3_Northwind_simple_220913_B_Suite3.zip

Export to SIARD with resulting file:

1.3b_1-3_Northwind_simple_220913_B_Suite3.zip