Data Sources are wiped/re-initialized every time the app is opened when using environment variables in database path
Data Sources are wiped/re-initialized every time the app is opened when using environment variables in database path
Hi,
As the title suggests, I have noticed that when using environment variables in the database path of a data source, the database is "initialized" every time the application is launched. As an example, if the database path is set to %USERPROFILE%\Documents\Connections.db, the database file is created and initialized as expected. It's initial size after initialization is 176kb. You can start making changes and adding entries/folders/etc to the database, and the size of the file will grow as expected.
When you close the application, the database size stays the size it was prior to the application being closed, after the modifications.
However, when re-opening the application, the configuration doesn't appear to read the environment variable correctly, and it will always attempt to initialize the data source as it's configured. This ends up wiping/re-initializing the data source you just created/modified, and you end up with a blank database, returned to its initial 176kb size.
All Comments (6)
Hello,
Thank you for reaching out to us regarding this,
Could you please specify the version of RDM you are currently using?
To clarify, all data sources mapped are removed from the File -> Data sources menu?
Let me know,
Best regards,
Samuel Dery
Hi Samuel,
Sorry, I re-wrote my initial post because it was appearing blank for me after submitting.
RDM version is 2024.3.17 64-bit -- I did notice this on at least 2024.1.x as well, though.
To clarify, the data sources in the file menu are still there as they were previously configured, but when the application is re-opened, it initializes the database again because it seems like it's not unfurling the path when an environment variable is being used -- and doesn't detect the database file for the data source as existing.
Further to this, it appears to only happen when using SQLite data source type, as opposed to XML. Changes to the XML data source type persist through application relaunch(es) and do not trigger the database file to be initialized/overwritten.
Hello Kevz,
we managed to reproduce the issue, a ticket has been sent to the Engineering Team.
Best Regards,
Antoine Mauger
Hello,
We've deployed a fix for this issue, which will be available in version 2024.3.19.0.
Regards
Jonathan Del Signore
Great! Love your work guys.