keeps/dbptk-developer

SIARD-->MYSQL-->SIARD: non existent candidate keys are created in output when exporting data to .siard. The workflow is as follows input.siard-->dbptk-->MySQL-->dbptk-->output.siard

ibbenz opened this issue · 1 comments

ibbenz commented

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 MySQL into .siard using dbptk-Desktop
  3. Compare the .siard data of the input and outputfile in SiardSuite

The difference between input and output-file:
New_Candidate_Keys_after_Export

Attach the dbptk-app.log.txt file below.
dbvtk.log

The input-file:
0_1-3_Northwind_simple_2022_07_10_dbptk_V06.zip

The output-file:
2022_07_10_dbptk_V06_MySQL2SIARD_dbptk.zip

ibbenz commented

It also occurs with microsoft SQL