<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dbeaver on VisorCraft News</title><link>https://www.visorcraft.com/news/tags/dbeaver/</link><description>Recent content in Dbeaver on VisorCraft News</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 03 Aug 2026 10:00:00 -0500</lastBuildDate><atom:link href="https://www.visorcraft.com/news/tags/dbeaver/index.xml" rel="self" type="application/rss+xml"/><item><title>Mongrel vs DBeaver: When the Database Client Becomes the Whole Workbench</title><link>https://www.visorcraft.com/news/2026/08/mongrel-vs-dbeaver-database-systems-workbench/</link><pubDate>Mon, 03 Aug 2026 10:00:00 -0500</pubDate><guid>https://www.visorcraft.com/news/2026/08/mongrel-vs-dbeaver-database-systems-workbench/</guid><description>&lt;p&gt;The database client is one of those tools that quietly accumulates complexity over time. You start with a query window and a results grid. Then you need SSH tunnels, so you add a separate terminal. Then you need to inspect an API response, so you open a different application. Then you need to check a container log, so you switch to Docker Desktop or a CLI session. What began as a focused database tool becomes a constellation of windows, credentials, and context switches.&lt;/p&gt;</description></item></channel></rss>