connect_to_database now enables DBI PrintError, which can emit database connection or SQL errors directly to STDERR/logs and may include operational details such as database names, hosts, or query context. The submitted change explicitly turns this on while also adding cleaned user-facing errors, so the extra raw warning output is likely unintended. Suggested fix: Use PrintError => 0 and capture RaiseError/eval or driver errstr for controlled, sanitized reporting instead of allowing DBI to print raw warnings.