Logging to stdout and externally-supplied connection information

[0cjs]

I've just started using DBeaver, and it seems great, but there are a couple of issues I'd like help with.

First, dbeaver seems to do a lot of logging to stdout or stderr: hundreds even thousands of lines over a session. Is it possible to reduce this noise so that the stuff showing up in the terminal where it's run is just the "important" stuff that a developer running DBeaver would care about? Certainly printing Start Eclipse Jobs Mechanism [org.eclipse.core.jobs 3.15.700.v20250725-1147] and the like on every startup is far from vital, and really not even useful. I start dbeaver from a script, and so have the ability to pass arbitrary command-line parameters to it and I'm hoping I can do something with that. It wouldn't be practical to tell developers to go around editing config files, though I suppose I could try to have the script auto-edit them. (That introduces its own problems, such as what to do when the config files don't exist because dbeaver has not yet ever been run.)

Second, he system I'm working with has a configuration file containing server connection configuration for many servers: development, staging, prod, etc. Some of the connection information can change frequently, e.g. the ports used by the development/unit test MySQL server may change every time the container running it is restarted.

Passing this connection information to DBeaver is easy; I have a script that takes the name of the server to which the developer wishes to connect (e.g. dev.mysql.dev, for the MySQL server in the development environment), looks up the connection information, and builds a connect string for -con (e.g. host=127.0.0.1|user=root|database=dev|port=32775|driver=mysql|name=dev.mysql.dev). But from investigating some error messages I've been seeing, such as "2025-12-06 12:45:48.472 - Datasource mysql8-19af1997dce-60a76de76d4acbd8 not found in project General (/General/Scripts/Script.sql)" it seems as if DBeaver may be referencing obsolete connection information from previous -con arguments. (But I'm not sure about this; an LLM suggested it.) Is there a way to clear that, or have the old connection data get updated by a -con with the same name=..., or something like that?

[0cjs]

For what it's worth, I did try using the save=true parameter, but despite me specifying the same connection ID with every run, it creates a new connection every time. (Setting create=false in conjunction with this leaves me with no connection at all.)