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

Don't seem to work with OLA 5.10 with internal database #42

Open
henrikadolfsson opened this issue Apr 27, 2019 · 2 comments

Comments

@henrikadolfsson
Copy link

commented Apr 27, 2019

The latest version of OLA (5.10.1) don't seem to be compatible with liveresults.

When trying to open a internal OLA db I get the following error alert:

image

It works fine when I downgrade to OLA 5.5 on the same competition.

@fredricj

This comment has been minimized.

Copy link
Contributor

commented May 3, 2019

In OLA 5.10 the internal database engine creates the internal database in a newer format with a different extension (.mv.db instead of .h2.db). The database engine expects the path without the extension so for the old format Emmaclient automatically removes the extension, but this doesn't happen for the newer format.
Workaround is to specify the database without the extension.
The fix is to update the code to handle the new extension as well.
In addition it should add IFEXISTS=TRUE to the connection to avoid autocreating a new empty database when a non-existing database is selected, which is what happened above

@fredricj

This comment has been minimized.

Copy link
Contributor

commented May 5, 2019

This should be fixed by #44 . So far I couldn't get the IFEXISTS=TRUE to work, it only gives an error message that it couldn't find the database

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.