ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #dbeaver
Learn when to use DBeaver's internal Data Transfer wizard versus native database dump tools to avoid memory errors and maximize export speed for large datasets.
DBeaver's ER Diagram works live and offline from migration scripts, with force-directed and hierarchical layouts, filtering, and PlantUML/Mermaid exports for version-controlled docs. Includes a Flyway-to-Markdown pipeline and real-world limits on layout persistence, large schemas, and implicit FKs.
Learn how to use DBeaver’s Data Transfer wizard to migrate tables between different database engines, including column mapping, batch size tuning, and verification steps.
DBeaver's Export Data wizard turns any table or query result into a CSV. Here's the configuration that round-trips cleanly, how to verify it, and where the client-side export breaks down.
Stop guessing how legacy tables relate. Learn how to use DBeaver's Virtual Foreign Keys to map undocumented databases and generate ER diagrams without modifying production schemas.
When connecting to a PostgreSQL instance over TLS using DBeaver, the client sometimes rejects the server's certificate despite the certificate being valid and trusted by the system Java keystore. The issue appears to be related to DNS resolution of the host name used in the connection string, which may cause a mismatch between the certificate's subject alter
DBeaver delegates DNS lookups to the underlying JVM, which caches results according to the networkaddress.cache.ttl system property. The UI does not expose a runtime control to invalidate that cache for a specific connection. Starting with DBeaver 23.3, a per-connection property useCustomTruststore allows distinct truststores per connection. The connection w
When configuring a DBeaver connection to use SSL with a self‑signed or private‑CA certificate, the user can enable the “Trust server certificate” option or import the certificate into the connection‑specific truststore. The intended goal is to allow the connection to succeed despite the certificate not being present in the Java default truststore. However, i
DBeaver allows users to toggle between Auto-commit and Manual-commit modes to manage transaction boundaries. While Manual-commit is intended to provide a safety net for data modifications, the behavior during schema changes (DDL) depends heavily on the underlying database engine's implementation. Certain database drivers trigger implicit commits the moment a