-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Exception occurred after connecting to shared database suggesting a duplicate entry #10336
Comments
Hi, sorry for the late response. which version of mysql or mariadb are you using? |
Hi, thank you for the answer. We are using this version : 10.3.37-MariaDB - Source distribution |
I'm having the same issue, but with PostgreSQL versions 15.4 and 16. |
I could reproduce it now locally and found the issue. There was an issue with parsing back the version of the metadata |
@ArnaudAcoucite @drescherflo Can you please test this verison? https://builds.jabref.org/pull/10494/merge |
Thanks Christoph! I tested this version, now I get this error message:
|
@ArnaudAcoucite Sorry, can you please download the updated version again (same link) Somehow did not commit the real fix yesterday |
I downloaded the updated version and now it works! Thank you very much! Maybe should I wait for @drescherflo to test it before closing the issue? |
The issue will be closed automatically once the fix is merged |
Just tested the build and can confirm that everything's working as expected. Thank you @Siedlerchr |
Ok great |
JabRef version
5.10 (latest release)
Operating system
Windows
Details on version and operating system
Windows 11 pro 64bit Version 22H2 Built 22621.2134
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
Appendix
Following the error message, we checked the tables JABREF_ENTRY and ENTRY on DBeaver but didn't find a duplicate entry.
Log File
The text was updated successfully, but these errors were encountered: