Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

siard-->microsoft sql: no candidate keys after conversion; no errors in dbptk.log #530

Open
ibbenz opened this issue Sep 22, 2022 · 1 comment

Comments

@ibbenz
Copy link

ibbenz commented Sep 22, 2022

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:

  1. Load the attached .siard-file (zip) into a Microsoft SQL Database
  2. Notice that there are no key-related error messages in dbptk desktop or its log-file
  3. 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
Copy link
Author

ibbenz commented Sep 28, 2022

The same issue occurs in case of MySQL and postgreSQL

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant