ibbenz

Results 14 issues of ibbenz

**Description of error:** I execute a import-export cycle with a SIARD-file and check finally if the data remained the same. However, DATE-type values are changed during this cycle, which results...

Description: Date and Time cannot be read properly into a MySQL database in the desired format. (siard to mySQL) Background: A study about the capabilities of dbptk, Fullconvert (Spectral Core)...

Description: Steps required to reproduce the bug: 1. Load any .siard 1.0 file with Elements into Microsoft SQL DB 2. Notice that there are no values of the in Microsoft...

**Description:** Non-existent candidate keys are created during downloading .siard-data in MySQL **Steps required to reproduce the bug:** 1. Upload Inputfile in MySQL with dbptk-Desktop 2. Export the uploaded data from...

Description: Candidate keys which were present in the SIARD-file are not created by dbptk during the process of loading the SIARD-file into the SQL-Database. Therefore, there are no candidate keys...

**Description:** Table 6 (Employees) of the SIARD-file 0_1-3_Northwind_simple_220913_B_dbptk3.siard contains a column of the datatype TIME. Uploading this column leads to the error: RESTException: Remote exception caused by GenericException: For input...

**Description:** RESTException: Remote exception caused by GenericExeption: caused by IlegalArgument Exception The error is caused by a column containing DATE-datatype values (Table 6 (Employees) in the attached SIARD-file). No such...

After starting up the dbptk-app the following errors occurred: **Errors:** WARN could not get type for name javax.xml.bind.annotation.adapters.XmlAdapter from any class loader Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException Caused by:...

Description: I want to upload a .siard-file into dbptk. I validated the file with KOST-Val. dbptk throws the following error: Could not import the metadata to the Solr instance: Metadata...

Description: A siard file is loaded with dbptk into a Microsoft SQL Database. No error message occurs during the transfer, but in the end only 2 out of 8 tables...