Connection error to a host other than localhost

[afls]

JabRef version 3.8.2 on Windows 7 (64 bit)

Hello,
using "Connect to shared database" to connect to MySQL on a host that is not localhost results to a "Connection error" message: "Access denied for user 'db@local-PC-name.de' (using password:YES)".

The menu "Connect to shared database" does not use the host name (server name) entered into the text field but always uses the local PC name. The same error message also occurs then entering not the host name but the IP of the server.

I hope that anybody can help or fix the problem, since using a shared database only at localhost does not make sense in a team with many users.

Regards, afls

[stefan-kolb]

@koppor Can you reproduce the behavior?

[koppor]

I usually tried postgres.

@stefan-kolb Can you quickly recommend me a free PaaS MySQL service to test?

[stefan-kolb]

This should not be related to MySQL, should it?

[stefan-kolb]

@koppor http://w2.cleardb.net/

[koppor]

@memering seems to be able to connect to a remote database. See #3736.

[stefan-kolb]

Thank you for your report 👍
However, I cannot reproduce this behavior on the current master. Can you please try the latest build from http://builds.jabref.org/master.

[memering]

It's an SSH tunnel in my case, so from JabRef's point of view it's localhost.

[stefan-kolb]

Cannot test it with Heroku Postgres as we don't support SSL #3419

[stefan-kolb]

Ok, i can connect to a JawsDB remote DB. However, I can hardly edit information as every step nearly freezes the UI. Is every change sent to the database, e.g., every key pressed?

[stefan-kolb]

In general this is functional but kind of unusable as every single event synchronizes with the database.

[koppor]

This design decision was per intention (somehow). It is event-triggered. I think, @lenhard once made an improvement at the event that only after a few character changes the event is fired. Maybe, we should update that DB sync code that only after a field is changed, the event is sent?

[stefan-kolb]

@koppor this problem is tracked in a separate issue #3736