What happened?
Importing connections from DBeaver drops the username, so imported connections have an empty user field.
Steps to reproduce
- Import connections from DBeaver
- Open an imported connection
- Username is empty
Expected behavior
The username imports correctly from DBeaver.
Code pointer
TablePro/Core/Services/Export/ForeignApp/DBeaverImporter.swift reads the user from two sources: config["user"] (credentials-config.json, line ~179) and properties["username"] (data-sources.json, line ~239). DBeaver stores the user under different keys across versions and credentials-config.json is AES-encrypted, so the lookup likely misses. Verify the key names and decryption path.
Database type
N/A
What happened?
Importing connections from DBeaver drops the username, so imported connections have an empty user field.
Steps to reproduce
Expected behavior
The username imports correctly from DBeaver.
Code pointer
TablePro/Core/Services/Export/ForeignApp/DBeaverImporter.swiftreads the user from two sources:config["user"](credentials-config.json, line ~179) andproperties["username"](data-sources.json, line ~239). DBeaver stores the user under different keys across versions and credentials-config.json is AES-encrypted, so the lookup likely misses. Verify the key names and decryption path.Database type
N/A