-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[H2 V.2] FOREIGN KEY CONSTRAINT appears to be treated as if it were a PRIMARY KEY CONSTRAINT #33201
Comments
Thank you for bug report and investigation |
LonwoLonwo
added a commit
that referenced
this issue
May 23, 2024
LonwoLonwo
added a commit
that referenced
this issue
May 23, 2024
MashaKorax
added a commit
that referenced
this issue
May 24, 2024
serge-rider
pushed a commit
that referenced
this issue
May 24, 2024
Co-authored-by: MashaKorax <[email protected]>
Foreign key recognition fixed. The fix will be available in release 24.1.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
It seems that the H2 V.2 Driver of DBeaver treats FOREIGN KEY CONSTRAINTs the same way as PRIMARY KEY CONSTRAINTs.
H2 V.2 or later versions, the value of the CONSTRAINT_TYPE column in INFORMATION_SCHEMA.TABLE_CONSTRAINTS is set to "FOREIGN KEY" for foreign key constraints, not to "REFERENTIAL".
(And it seems that this specification change has not yet been reflected correctly in the documentation for H2 V.2.)
It seems that this specification change is affecting methods, for example, such as prepareUniqueConstraintsLoadStatement() and getUniqueConstraintType() in org/jkiss/dbeaver/ext/h2/model/H2MetaModel.java.
DBeaver Version
Community Edition 24.0.4
Operating System
Windows 10 Pro 22H2 build 19045.4412
Database and driver
H2 Embedded V.2 (2.2.224)
Steps to reproduce
Additional context
No response
The text was updated successfully, but these errors were encountered: