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

Create blog entry for shared database support #1

Open
koppor opened this issue Aug 9, 2016 · 4 comments
Open

Create blog entry for shared database support #1

koppor opened this issue Aug 9, 2016 · 4 comments

Comments

@koppor
Copy link
Member

koppor commented Aug 9, 2016

See JabRef/jabref#1451 for the code.

  • Automatic change push to the server via EventBus. (Support for all kinds of EntryEvents, see AddEventSystem jabref#1028)
  • Full synchronization support for MySQL, PostgreSQL and Oracle
    (manual and semi-automated pull)
  • Conflict avoidance by version control and Optimistic Offline Lock
  • Connection loss handling
  • Switch to offline working mode

open_rem_db

shareddb_sc1

shareddb_sc2

shareddb_sc3

conn_lost

One can test the feature using https://www.freemysqlhosting.net.

@mairdl
Copy link
Contributor

mairdl commented Aug 22, 2016

@koppor on slack you asked for a help.jabref.org entry but here you ask for a blog entry, do you want them both or do you want us to create a blog entry that can be used for a help entry?

@koppor
Copy link
Member Author

koppor commented Aug 22, 2016

In the end, I want both. Based on the experiences of JabRef/www.jabref.org#58 and that the help page is the longer lasting asset, I stick with asking you for a help page.

@koppor
Copy link
Member Author

koppor commented Sep 19, 2016

The help file is available at http://help.jabref.org/en/SQLDatabase

@koppor
Copy link
Member Author

koppor commented Apr 13, 2017

Blocked by JabRef/jabref#2689

Maybe these issues should be solved before making advertisements for the feature: https://github.com/JabRef/jabref/issues?q=is%3Aopen+label%3Ashared-database

Siedlerchr pushed a commit that referenced this issue Jul 5, 2021
koppor pushed a commit that referenced this issue Aug 21, 2024
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

2 participants