bug in driver manager

Thomas, The Driver Search Paths are used by DbVisualizer to find jar files that match the pre-defined driver definitions in the driver manager. If there are bundled driver jar files in DbVisualizer these will replace any custom loaded jar files for these driver definitions. I assume you are using the PostgreSQL driver definition in the driver manager to load your own jar files? Based on this and since there is a bundled jar file for PostgreSQL these manually loaded jar files will be replaced when upgrading version as you've already discovered. What you should do is create your own "My PostgreSQL" driver definition in the driver manager and load your jar file with it instead. DbVisualizer will not touch these custom definitions. Also, loading multiple versions of the same driver jar files in a single driver entry is not recommended even if it works. What will happen is that DbVisualizer will pick the first jar file when it loads the driver at connect. A better setup is to create a "My PostgreSQL 9.0" entry with the 9.0 driver jar and a "My PostgreSQL 9.1" entry with the 9.1 driver jar and so on. Then you will be sure what driver version is used when connecting. I hope this helps. Regards Roger

Thomas, To ease the process of changing all drivers: 1) Create the "My PostgreSQL" (or the name you prefer) driver in the Driver Manager 2) Quit DbVisualizer 3) Open /home//.dbvis/config70/dbvis.xml in a text editor and replace all: PostgreSQL to My PostgreSQL 4) Save the file 5) Start DbVisualizer Regards Roger