-
Notifications
You must be signed in to change notification settings - Fork 108
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
JDBC backend differs in behaviour with JE backend #471
Comments
please check in 4.9.2 |
Afraid, this hasn't fixed the issue. Is there anything in the logs to pinpoint the original entry causing this? |
Please attach script for reproduce |
Will prepare custom data to replicate this with JDBC back-end. |
please provide "Steps to reproduce" the behavior like: OpenDJ/.github/workflows/build.yml Lines 89 to 99 in b0f3e79
and attach files with data, logs, screenshots |
Describe the bug
JDBC
back-end type throws unique constraint violation while loading same set of entries as inJE
back-endTo Reproduce
Steps to reproduce the behavior:
mail
attributepostgresql
)Unique constraint violation
error.Expected behavior
The entries should be successfully added to LDAP as is the case in
JE
.Screenshots
NONE
Desktop (please complete the following information):
macOS
4.9.1
Additional context
Seems like on database side all INDEXES have UNIQUE and PRIMARY constraints.
The text was updated successfully, but these errors were encountered: