Skip to content

Latest commit

 

History

History
57 lines (42 loc) · 3.52 KB

SQLDatabase.md

File metadata and controls

57 lines (42 loc) · 3.52 KB
title helpCategories since
Shared SQL Database
Collaborative work
3.6

Shared SQL Database

JabRef is able to support collaborative work using a shared SQL database. This feature is available since JabRef 3.6. If you used to work with an older version of JabRef, please refer to SQLDatabaseMigration for information how to update your data.

Usage

To use this feature you have to connect to a remote database. To do so you have to open File in the menu bar and then click the Connect to shared database item. The Connect to shared database dialog will open and you will have to fill in the shared's database connection settings. Under the field Database type you can choose between PostgreSQL (at least version 9.1), MySQL, and Oracle depending on your shared database. Then, you have to fill out the remaining fields with the according information. If you like you can save your password by clicking the Remember password? checkbox.

Screenshot of Connect to shared database dialog

After connecting to your shared database, your main window should look like this:

Screenshot of JabRef with an open shared database

JabRef will automatically detect your changes and push them to the shared side. JabRef will also constantly check if there is a newer version available. If you experience connection issues, you can pull changes from your shared database via the icon in the icon bar. If a newer version is available, JabRef will try to automatically merge the new version and your local copy. If this fails, the Update refused dialog will show up. You will then have to manually merge using the Update refused dialog. The dialog helps you by pointing out the differences, you then will have to choose if you want to keep your local version or update to the shared version. Confirm your merge by clicking on Merge entries.

Screenshot of Update refused dialog

The Update refused dialog can also take a different form, if the BibEntry you currently work on has been deleted on the shared side. You can choose to keep the BibEntry in the database by clicking Keep or update to the shared side and click Close.

Screenshot of Update refused dialog due to a deleted entry

If you experience a problem with your connection to your shared database, the Connection lost dialog will show up. You can choose to Reconnect, Work offline or Close database. Most of the time simply reconnecting will fix this problem, if that's not the case you will have to choose between Work offline or Close database. Pick Work offline if you want to make sure your changes are saved. If you think there is nothing to save just pick Close database. If you choose to work offline, JabRef will convert the shared database to a local .bib database. Since you are no longer working online, but instead on a local database, you will have to import your work via copy and paste into the shared database. However before you import it into the shared database, make sure to check if changes happened during your offline time. Otherwise you might override someone else's work.

Screenshot of Connection lost dialog

Try it out

You can test the shared SQL database support by using https://www.freemysqlhosting.net for MySQL and https://www.elephantsql.com/ for PostgreSQL.