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

[BUG] 5.0 : NamedConstraint.getType() incorrectly returns "UNIQUE KEY" for UNIQUE still exists #2082

Open
rasa-app opened this issue Sep 27, 2024 · 0 comments

Comments

@rasa-app
Copy link

Failing SQL Feature:

This is related to #1164 and happens when UNIQUE is after FOREIGN KEY

SQL Example:

  • Simplified Query Example, focusing on the failing feature
    CREATE TABLE employees (
    employee_number    int         NOT NULL
    , employee_name    char (50)   NOT NULL
    , department_id    int
    , salary           int
    , PRIMARY KEY (employee_number)
    , FOREIGN KEY (department_id) REFERENCES departments(id)
    , UNIQUE (employee_name));

Software Information:

  • JSqlParser version : 5.0
  • Database (e. g. Oracle, MS SQL Server, H2, PostgreSQL, IBM DB2 )
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant