-
Notifications
You must be signed in to change notification settings - Fork 3
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
Get rid of SQLite in favour of MySQL #7
Comments
I know, though thanks for reporting this as an issue. MMWatch now uses an SQLite database for storing data. It is known for a bad concurrency. These errors happen when there is an update going on in the background, once every three minutes, so the frontend cannot read the locked database. Nothing is broken, and when you reload in 10-15 seconds, it should work. Although I really would need to convert the datatabase to mysql. |
Do we have sqlite dump available somewhere? I can try to convert it to mysql sql-based dump. |
There is an issue with MySQL: full unicode support needs 4 bytes per character, and one of the indexed fields is 255 chars long. But MySQL cannot use indexed varchar fields longer than 768 bytes. The production instance at maps.me uses PostgreSQL, not sure how to do this on osmz.ru yet. |
Hi,
very often when I use mmwatch there is a
It is not a serious issue. No details for the error are provided, so I can't submit a better report/patch.
Thanks.
The text was updated successfully, but these errors were encountered: