@chpietsch @liaizon @dev Thanks for the feedback, I will try to improve that.
In case you still have the config file with which you produced the error, it would be great if you could send that my way.
Because judging from the error, it parsed the file correctly but it was actually the database driver that got confused.
With the repro file I could try to just do some checks on the database string to prevent these unhelpful messages