DBeaver Workspace Migration Driver Compatibility During Rollback

Workspace version isolation and driver directory separation

DBeaver creates a new version-specific workspace directory (for example ~/.dbeaver5) during a major upgrade and attempts to migrate connections, scripts, and preferences from the previous workspace. The bundled JDBC drivers, however, reside inside the DBeaver installation folder rather than the workspace. When a rollback is performed by deleting the new workspace and restoring the old one, the installation directory still contains the newer driver versions that shipped with the upgraded release.

Unresolved constraint

There is no documented mechanism that automatically downgrades or isolates drivers to match the restored workspace. The migration wizard also does not validate whether saved passwords or SSH tunnel configurations remain compatible with the encryption libraries in the older version.

Specific questions

1. Which driver files must be manually reverted alongside the workspace to guarantee connection compatibility after a rollback?
2. Does the migration wizard expose any flag or log that records which driver versions were active before the upgrade?
3. Can a portable installation layout be used to atomically restore both workspace and driver set without affecting system-wide file associations?