siard-->microsoft sql: no candidate keys after conversion; no errors in dbptk.log
ibbenz opened this issue · 1 comments
ibbenz commented
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 in the
SQL database which were present in the SIARD-file.
Steps required to reproduce the bug:
- Load the attached .siard-file (zip) into a Microsoft SQL Database
- Notice that there are no key-related error messages in dbptk desktop or its log-file
- Notice that none of the candidate keys has been created in e.g. Tables "order details" or "categories"
Attach the dbptk-app.log.txt file below:
dbvtk.log
The siard-file:
0_1-3_Northwind_simple_220913_B_dbptk.zip
ibbenz commented
The same issue occurs in case of MySQL and postgreSQL