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

DBeaver not reading SQLite composite foreign keys correctly #29309

Open
CommunyAS opened this issue May 2, 2024 · 1 comment
Open

DBeaver not reading SQLite composite foreign keys correctly #29309

CommunyAS opened this issue May 2, 2024 · 1 comment

Comments

@CommunyAS
Copy link

Description

Since the release of DBeaver-Community 23.3.2 DBeaver does not read composite foreign keys in a SQLite database correctly - it worked perfectly before until version 23.3.1.
The problem persist until the latest version 24.0.3

The problem is that DBeaver seems to mixe up the columns referencing two table if it is defined with a composite foreign key.

In the screenshot below one can see that the integer value 42 and the text string RAHal2 turn up at the wrong place in the command line generated by DBeaver (as indicated with the red arrow). Consequently, this results in an error message, since RAHal2 is not put in parentheses and there interpreted as column - but in fact it is the field value of column ID_FSTkurz (vise versa with 42 and ID_Bef)

SQL Error [1]: [SQLITE_ERROR] SQL error or missing database (no such column: RAHal2)

Screenshot 2024-05-02 at 11 35 09

The composite screenshot with parts of the DDLs of both tables provides information on table definition with focus on primary and foreign keys.

Screenshot 2024-05-02 at 11 54 47

I aware that it might not be best practice to use composite primary/foreign keys, but for my purposes I deem it necessary.

DBeaver Version

Community Edition 24.0.3.202404211624

Operating System

macOS Sonoma 14.4.1

Database and driver

  1. SQLite
  2. Driver: SQLite JDBC 3.45.3.0 (org.xerial:sqlite-jdbc:RELEASE 3.45.3.0)

Steps to reproduce

No response

Additional context

error.log

@E1izabeth
Copy link
Member

Thank you for bug report.

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

No branches or pull requests

4 participants