You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that I managed to connect to mysql, the next challenge is to upgrade the db schema. Our installation tells me to be version 1.58.15; the db.schema.version is 20041114 (from the configuration table).
I tricked the SchemaVersion.update() by adding a schema.id property with value "200411" to actually perform the update, but it seems to work only partly. I have my users and the hierarchy, and am able to login, but no passwords are displayed. So I suppose some schema upgrades from at least "20041114" until "201112" are missing.
Any chance that you could bring the missing steps into the new version?
For a little background, we obviously still use the EPS. However, it became dead slow lately. Especially seaching can take several minutes. Apparently, the history has grown to big over time, and there seems to be not obvious way to wipe older entries from the db to speed things up. Besides hoping for speed, the new interface looks way more user friendly and intuitive.
Thanks
Sascha
The text was updated successfully, but these errors were encountered:
Now that I managed to connect to mysql, the next challenge is to upgrade the db schema. Our installation tells me to be version 1.58.15; the db.schema.version is 20041114 (from the configuration table).
I tricked the SchemaVersion.update() by adding a schema.id property with value "200411" to actually perform the update, but it seems to work only partly. I have my users and the hierarchy, and am able to login, but no passwords are displayed. So I suppose some schema upgrades from at least "20041114" until "201112" are missing.
Any chance that you could bring the missing steps into the new version?
For a little background, we obviously still use the EPS. However, it became dead slow lately. Especially seaching can take several minutes. Apparently, the history has grown to big over time, and there seems to be not obvious way to wipe older entries from the db to speed things up. Besides hoping for speed, the new interface looks way more user friendly and intuitive.
Thanks
Sascha
The text was updated successfully, but these errors were encountered: