You can see all of the currently assigned local variables for SQL Editor. You need to click a “Show SQL variables” button in the SQL editor.
A new tab alongside Output and Execution log panels will be opened with a list of assigned variables. On this panel, you can also show assigned parameters by clicking the corresponding button. (Note: toolbar is customizable. See Toolbar Customization)

Tip: Read more about pre-configured variables in our article

Manipulating variables

You can change values for the current variable using the variables tab. Simply click on a variable’s row and edit its value in the window below. To delete or add a variable or parameter, you can use a corresponding button. Instead of typing @set or @unset, you can use these buttons in the script.

If you have a long list of variables, you can click a magnifying glass to initiate a search bar. Start typing either a variable’s name or its value to filter the list.

Moving a panel

Variables panel is always connected to output and execution log panels, but this group of tabs can be configured to be shown either at the right side of the editor or at the bottom alongside the results panel. By default, the panels are shown on the right side. To change their location you need to either check or uncheck Show panels in result tabs in the context menu.

Views are windows within the workspace that provide presentations and ways to navigate the information. The main views in DBeaver are: Database Navigator, Projects and Project Explorer.

To open a view:

• On the Window menu, click Show View and then, on the submenu, click the name of the view. Click Other if the view is not visible on the submenu.
• For Database Navigator, Projects, and Project Explorer views, on the Window menu, just click the name of the view.

Some views open on demand, for example the Search view opens to show search results.

Views provide their own toolbar and menu:

To open the view menu, click the View Menu button in the upper-right corner of the view’s title bar, next to the Minimize button.

The toolbar contains buttons applicable to the objects displayed in the view. The set of enabled and disabled buttons depends on the object in focus.

Views also provide context menus for objects they display. To open a context menu for an object, right-click the object.

Overview

The virtual key feature in DBeaver allows you to save changes to tables that do not have a primary key or unique index. You can define a virtual key, which is a set of columns that form a unique combination of values. This ensures each row can be uniquely identified, allowing you to save changes to the table.

Note: Virtual keys exist only in DBeaver, not in the database itself. You can define these keys even if your database does not support them.

Tip: All virtual entities are stored in the

data-sources.json

file. For more information, refer to the Configuration Files article.

Virtual key management

Use virtual keys to handle data updates and relationships in tables that don’t have physical primary or foreign keys.

Accessing the virtual key configuration window

You can access the settings for configuring virtual keys through two different methods:

1. Properties Editor:

   1. Navigate to the Properties Editor.

   2. Select the Virtual tab from the Tabbed editors.

      

2. Data Editor:

   1. Right-click in the Data Editor.

      • Select Logical structure to view different options for virtual entities.
      • You can either choose a specific option from the list or click on Edit to open the configuration window where you can manage virtual entities.

      

Note: When creating a connection in the Connection Details, ensure the checkbox for Show virtual model Editor is selected to access virtual key features.

Creating a virtual unique key

Inserting new rows into a table that do not have a primary key or unique index can generally be completed without issues, but updating existing data can be tricky. A virtual primary key helps you update data by acting as a unique identifier for rows in tables without a physical primary key.

1. Navigate to the Virtual Unique Key settings.

2. Configure the options:

   

   Field/Checkbox	Description
   Table	Automatically filled with the name of the table being modified.
   Name	Enter a name for the virtual key.
   Use All Columns	Check this to include all columns from the table in the virtual unique key.
   Columns List	Displays columns available for selection.
   Select All	Button to quickly select all columns in the Columns List.

   Important: Be careful with the Use All Columns option. It may cause changes in multiple rows if the columns do not uniquely identify each row.

3. Click OK to save the virtual key.

Error handling during data modification

If you begin modifying data in a table that lacks a primary or unique key, DBeaver will alert you with the following error message:

You can handle the error in one of two ways:

• Use All Columns: Selecting this option immediately treats all columns as a virtual key.

  Important: Use this option carefully, as it may cause changes in multiple rows if the columns do not uniquely identify each row.

• Custom Unique Key: Alternatively, you can create a more specific virtual unique key by choosing Custom Unique Key. For more information on creating a virtual unique key, refer to the Creating a virtual unique key section.

Creating a virtual foreign key

Virtual foreign keys are useful in databases where physical foreign key constraints are not present. They allow you to define and enforce relationships between tables virtually, ensuring data integrity.

1. Navigate to the Virtual Foreign Key settings.
2. Click Add to start defining a new foreign key.

3. Define the foreign key details:

   

   Field/Option	Description
   Table	Automatically displays the name of the current table.
   Reference table container	Select the schema of the reference table.
   Reference Table	Choose a table to reference. Selecting a table updates the Unique key and Columns fields.
   Unique key	Displays keys available in the reference table. Select one that the foreign key will link to.
   Columns	Customize which columns in your table map to columns in the reference table. Options in this dropdown are based on the selected unique key. Select <new> to create a new mapping or choose existing columns to modify their mapping.

4. Click OK to create the foreign key.

Tip: You can also create virtual foreign keys in the ER Diagrams by dragging and dropping columns. This shows the foreign key connections between tables visually, making it easier to see how your database is structured.

Editing virtual keys

To modify or delete existing virtual keys, follow these steps:

1. Access the Configuration Window as detailed in the section Accessing the virtual key configuration window.
2. Choose the virtual key you wish to modify.
   • To make changes, select Edit and adjust as needed.
   • To delete, choose Remove.

Note: Virtual foreign keys cannot be edited once created; they can only be removed if changes are needed.

Settings for missing keys

To configure how DBeaver handles tables without unique keys, navigate to Window -> Preferences -> Editors -> Data Editor. Here are the options:

Option	Description
Use all table columns as a key upon saving	Utilizes all columns as a unique key.
Disable data editing	Prevents editing on tables without a unique key.

Expression language

You can use standard JavaScript-like expression language. DBeaver uses the Jexl engine to process expressions.
Language references and examples can be found here: http://commons.apache.org/proper/commons-jexl/reference/syntax.html

Column values

All columns’ values in the current result set can be referred to by name. Expression

will produce the sum of two numeric columns or concatenation of two string columns and .

Standard functions

Standard functions are declared in namespaces.
You can refer to the functions in the namespaces as variables –

).

math

You can access all math functions as

.
You can find all supported math functions here: https://docs.oracle.com/cd/E12839_01/apirefs.1111/e12048/functmath.htm

geo

Function	Parameters	Description
wktPoint	(longitude, latitude)	Produces WKT (geometry) point out of two coordinates. Default SRID is 4326.
wktPoint	(longitude, latitude, srid)	Produces WKT (geometry) point out of two coordinates and SRID

content

If you have JSON or XML columns in your table, you can add a virtual column with an expression for these columns.

Use content.json()[parameter1][parameter2] pattern to create expression for JSON column.

Expression example:

You can read more about JSON parameters in the link on the top.

Use content.xml(columnName, “expression”) or content.xml(columnName, “returnType”, “expression”) patterns to create expression for XML column. The quotation is important for parsing processes. XML expression can return types: string, number, boolean, node, nodeset – all these types can be used (!in quotes) for return data type clarification. content.xml(columnName, “expression”) returns string by default

Expression example:

You can read more about XPath here: https://en.wikipedia.org/wiki/XPath

Defining virtual keys

In cases where a table lacks a unique key, DBeaver provides the functionality to define a virtual key. This feature allows the creation of a custom set of columns that act as a unique identifier for table rows, facilitating the saving of changes in the absence of traditional unique constraints.

Refer to the Virtual Keys documentation for additional details on configuring and using virtual keys.

Note: This feature is available in Lite, Enterprise, Ultimate and Team editions only.

Overview

The Visual Query Builder in DBeaver is a visual tool that helps you build and understand SQL queries in complex databases. It lets you work with your database in a visual way, making it easy to see how tables connect and how data flows between them. This tool is useful when you want to create queries without writing SQL code yourself. The Visual Query Builder in DBeaver automatically converts your visual selections into SQL scripts, making it easier to explore and work with your data.

Getting started

To start using Visual Query Builder, click the Builder button in the SQL Editor for the desired database.

Tip: You can switch between the SQL Editor and the Visual Query Builder easily. If you write a valid SQL query in the SQL Editor, it will show up in the Visual Query Builder. The same way, any query you build visually will appear in the SQL Editor.

Visual Query Builder interface

The Visual Query Builder interface consists of the following sections:

• Workspace: This area displays all the tables, columns, and their relationships that you have added to your query.

• Palette: The Palette shows tools to interact with tables, and the section below displays the tables you have already selected and moved into the Visual Query Builder workspace.

• Query settings window: This section displays the Query settings, where you can configure columns, conditions, joins, sorting, and other settings related to your query.

Executing queries

The Visual Query Builder works in a similar way to the SQL Editor when you run queries.

• Click the Execute SQL statement button to run your query. You will see the results in the same tab.
• You can also use the Execute SQL statement in new tab button to run the query and open the results in a new tab.

You will find both buttons on the vertical toolbar of the Visual Query Builder, giving you easy ways to run your queries and view the results.

Note The toolbar is customizable. For more information, see Toolbar Customization.

Query configuration

The Visual Query Builder allows you to easily add tables, set query conditions, and customize how your query results are displayed using the Query settings available at the bottom of the workspace. These settings provide options for filtering, sorting, selecting columns, and setting join conditions, giving you full control over your query results.

To open/close the Query settings window, click the QUERY button .

Tip: You can toggle the visibility of the generated SQL query text by using the Show/hide generated SQL query text button on the right side of the window or by pressing Ctrl+B (⌃B for macOS).

Below are the sections explaining how to work with the Visual Query Builder capabilities in more detail:

Tables

You can add tables to the Visual Query Builder workspace using one of the following methods:

1. Drag-and-Drop: Drag the tables from the Database Navigator into the Visual Query Builder workspace.

2. Using the Palette:

   • In the Pallete menu, select Add Table from the Tools section.
   • Click on the Visual Query Builder workspace and choose the necessary table.

Columns

By default, all columns (

) from the tables you add are selected. To customize use the following methods:

Selecting columns in the workspace

• Click the checkboxes next to the column names in the table within the Visual Query Builder workspace to include or exclude columns from your query.
• The SQL script will update automatically in the SQL script area, reflecting your selections.

Using the Columns tab in the Query settings

• Select the Columns tab in the Query settings. In this tab, you can specify details related to the columns:

  	Option	Description
  	Column	Select the desired column for your SELECT statement from the dropdown list.
  	Alias	Provide a custom name for the column.
  	Grouping	Define grouping for aggregated data.
  	Aggregation	Select an aggregation function (e.g., COUNT , AVG , MAX , MIN , SUM ) to process the selected data.

Adding and removing columns

• Adding a Column: Press the Add button . A new column will be added to the query. Click on the first cell in the Column or Expression column and select a column from the dropdown list that appears.

  

• Removing a Column: To remove a column, click on the row containing its name and press the Remove button .

Adjusting column order

Use the Move Up/Down buttons to change the display order of columns in the result table. This will adjust the sequence in which the columns appear in your query.

Aliases

You can set a user-friendly name for your columns by clicking on a cell in the Alias column and entering the desired name. This alias will be reflected in the SQL script area and the final query result.

Grouping and aggregation

• If you want to apply a grouping condition, click the checkbox in the Grouping column row. This action will update your expression automatically. Other columns will become aggregated, and if there are no other columns, a

  COUNT(*)
  expression will be added.

• You can select different aggregation functions from the dropdown list or manually enter your preferred function in the cell.

Tip When you remove columns, they are also removed from the grouping expression. Any newly added columns will be automatically included in the grouping expression.

Conditions

You can add conditional expressions using the Conditions tab, which allows you to manage query conditions by filtering your query results.

• Select the Conditions tab in the Query settings. In this tab, you can specify details related to the columns:

  Setting	Description
  Left Operand	Defines the left operand of the conditional expression. This can be a column or a numeric value.
  Operation	Specifies the comparison rule (e.g., = , > , LIKE ) to apply between the left and right operands.
  Right Operand	Defines the right operand of the expression, which can be a column, numeric value, or string.

  

Adding and removing conditions

• Adding a conditional expression: Click the Add button on the right side of the tab. This action will create a new condition row, and a default

  WHERE
  clause will be automatically added to the SQL script area.

• Removing a conditional expression: To remove an existing condition, select the row containing the condition you wish to delete and click the Remove button on the right side of the tab.

Joins

When you add a table to the Visual Query Builder workspace, the joins are created automatically based on existing relationships:

• Automatic Joins: If the table you add has an existing relationship with one or more tables already in the workspace, the join will be displayed automatically.

• Inner join behavior: If the table does not have any existing relationship with the tables already in the workspace, the system will create a

  SIMPLE JOIN
  with the first table you added to the workspace.

Tip: You can disable automatic joins based on foreign keys in the Miscellaneous tab by unchecking the Auto-create joins according to foreign keys option. For more information, see Miscellaneous section.

Modifying joins

To modify joins:

• Right-click on the connection line between tables in the workspace to open a context menu. This menu allows you to change join types but is limited to modifying

  Left
  ,
  Right
  , and
  Full
  joins.

• Open the Joins tab in the Query settings to manage and adjust join settings for all tables in the workspace. In this tab, you can work with the following columns:

  	Setting	Description
  	Table/Conditions	Displays the tables involved in the join along with the join conditions.
  	Type	Allows you to modify the join type (e.g., Simple , Inner , Left , Right , Full , Cross , Natural ).
  	Alias	Lets you define a custom name for the join.

  

Sorting

You can set the order of rows in the result table.

• Select the Sorting tab in the Query settings. In this tab, you can specify details related to the columns:

  Setting	Description
  Conditions or Expressions	Click on the first cell in this column to display a drop-down list of all available columns. Select the column you want to sort by clicking on its name.
  Order	Defines whether the selected column should be sorted in ascending or descending order.

  

Adding and removing sorting conditions

• Adding a sorting condition: Click the Add button on the right side of the tab. This action will create a new sorting row, and a default

  ORDER BY
  expression will be automatically added to the SQL script area.

• Removing a sorting condition: To remove an existing sorting condition, select the row containing the condition you wish to delete and click the Remove button on the right side of the tab.

Miscellaneous

You can configure additional settings in the Miscellaneous tab.

Setting	Description
Add table aliases	Enable or disable the automatic generation of aliases for tables by selecting this check-box.
Use fully qualified table names	Use full table names (including schema) by selecting this check-box, which disables auto-completion for table names.
Auto-create joins according to foreign keys	Enable or disable the automatic creation of joins based on foreign key relationships.
Autosave on SQL-editor switch	Enable autosave when switching between SQL editors by selecting this check-box.

Overview

The interface language of DBeaver can be customized to suit your preferences. There are two methods to achieve this:

Changing interface language in preferences

1. Navigate to Window -> Preferences -> User Interface.

   

2. Choose your desired language from the drop-down menu.

3. Click the Apply and Close button to save your settings.

Note: If DBeaver is installed in a directory without write permissions, you may not be able to change the language directly through the interface. If this occurs, please proceed to modify the configuration file as described below.

Changing interface language in configuration file

1. Locate the

   dbeaver.ini
   file.

   Tip: Detailed instructions on finding

   dbeaver.ini

   are available in our article.

2. Using a text editor, open this file to make changes.

3. Insert the following lines above the

   -vmargs
   line:

-nl

XX

Replace

with the language code from the list below:

Language	Code
English	en
Arabic	ar
French	fr
German	de
Italian	it
Japanese	jp
Korean	ko
Portuguese (BR)	pt_BR
Romanian	ro
Russian	ru
Simplified Chinese	zh
Spanish	es
Traditional Chinese	tw
Ukrainian	uk

Overview

DBeaver Ultimate Edition is perfect for users who require a powerful set of tools for managing complex data environments and are also seeking enhanced cloud capabilities. This edition builds on the features of the Enterprise Edition by adding specialized tools for cloud database management and Kafka data streams. It offers seamless integration and efficient management of cloud data sources, making it an excellent choice for users who need to extend their data handling into the cloud.

Note: The DBeaver Ultimate Edition is designed for individual use only.

Ultimate Edition features

The Ultimate Edition offering unique capabilities designed for complex, multi-platform data management tasks with a strong emphasis on enhanced cloud integration:

• Cloud Explorer: A tool for managing and connecting cloud-hosted databases. Learn more
  It offers integration with various cloud services:

  • Amazon Web Services Learn more
  • Google Cloud Platform Learn more
  • Microsoft Azure Learn more

• Cloud Storage support: Enables file management within cloud environments of Amazon Web Services and Google Cloud Platform. Learn more

• Kafka support: Provides integration with Apache Kafka.

Advanced Enterprise features in Ultimate Edition

In addition to its unique features, the Ultimate Edition utilizes all the advanced capabilities from the Enterprise Edition, including:

• Data visualization

  • Data filtering and sorting: Provides tools to filter and sort data directly within the database interface. Learn more.
  • Color coding and highlighting: Simplifies data analysis by color-coding and highlighting table rows and fields based on conditions. Learn more.
  • Functional panels: Enhance data manipulation by offering additional space in the Data Editor for managing complex data types, accessible via tabs in a dedicated panel. Learn more.
  • Tableau integration: Facilitates integration with Tableau for advanced data visualization and analysis. Learn more.

• Query development

  • SQL Editor: Provides code completion for easier writing, auto-formatting, spelling checks, and support for variables. Learn more.
  • Execution plan visualization: Provides detailed visualizations of SQL execution plans. Learn more.
  • Additional tools for query creation:
    • Visual Query Builder (VQB): Provides a graphical interface to construct SQL queries without writing code. Learn more.
    • AI assistant: Integrates an AI assistant and AI Chat to offer guidance and automation within the SQL Editor. Learn more.
  • SQL debugger: Offers an SQL debugger specifically designed for PostgreSQL, aiding in query development and troubleshooting. Learn more

• Administrative tasks

  • Reverse engineering (ERD): Provides capabilities for reverse engineering databases into entity-relationship diagrams. Learn more.
  • Forward engineering:
    • Metadata editor: Enables the management and editing of database metadata.
    • Edit mode for ER-Diagrams: Offers functionalities for editing entity-relationship diagrams to aid in database design. Learn more.
  • Administrative tools:
    • Backup and Restore: Offers functionalities for backing up and restoring databases, ensuring data safety. Learn more.
    • Analyze and vacuum: Tools for optimizing database performance by analyzing and vacuuming database objects.
  • Permission and user management: Manages database permissions and user accounts.
  • Schema comparison: Provides tools for comparing database schemas either within the same database or across different databases. Learn more.
  • Data comparison: Offers tools for comparing data across databases or within different parts of the same database. Learn more.
  • Mock data generator: Provides tools for generating mock data, useful for testing and development purposes. Learn more.

• Data migration

  • Export and Import from files: Supports data export and import in up to 10 different file formats. Learn more.
  • Direct transfer between databases: Provides tools for efficient data migration directly between different databases or systems. Learn more.

• Security

  • Database authentication: Implements database authentication mechanisms to secure access.
  • Master and Project Password:
    • Master password: Enables the use of a master password to enhance security across the DBeaver. Learn more.
    • Project password: Facilitates the use of project-specific password to secure projects. Learn more.

• Automation

  • Task manager: A tool for managing and monitoring database tasks, enhancing productivity and organization. Learn more.
  • Task scheduler: Allows for scheduling database tasks, automating routine operations. Learn more.
  • Git integration: Supports integration with Git for version control, and change tracking. Learn more.

Subscription model

The DBeaver Ultimate Edition is offered as an annual subscription, which should be renewed to continue receiving updates and support.

Discover more about the DBeaver Ultimate Edition and subscribe.

Integrated database drivers

The Ultimate Edition has a comprehensive set of JDBC drivers, offering connectivity to various databases without needing separate downloads and configurations. Additionally, a versatile ODBC driver is supported for broader database compatibility.

For additional details on utilizing the ODBC driver, please consult the ODBC-JDBC driver article.

This edition also includes the Cloud Explorer feature, which provides access to cloud databases such as those on Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure. Cloud Explorer enables centralized authentication and automatic configuration, simplifying the management of cloud database connections.

Cloud Explorer databases

For a list of supported databases, please refer to the related section in the Cloud Explorer guide.

Supported databases

The Ultimate Edition provides support for a wide range of databases. Below are tables listing the databases available and specifying whether the Ultimate Edition offers enhanced features compared to the Community Edition.

* Enhanced features may include additional metadata capabilities, such as the ability to manage and interact with specific database objects unique to certain systems. For instance, managing Datashares in Redshift or handling Sequences** in Netezza. These features also cover various advanced authentication methods, and numerous other functionalities designed to improve security and data management.

Relational databases

Database name	Enhanced features* compared to the Community Edition	Available through Cloud Explorer
Altibase	–	–
Apache Arrow	Not available in Community Edition	–
Apache Calcite Avatica	✓	–
Apache Kylin	–	–
Azure Databricks	✓	–
Azure SQL Server	✓	✓
Babelfish via TDS (beta)	✓	–
CUBRID	✓	–
Cache	–	–
ClickHouse	–	–
ClickHouse (Legacy)	✓	–
CloudSQL – MySQL	Not available in Community Edition	✓
CloudSQL – PostgreSQL	Not available in Community Edition	✓
CloudSQL – SQL Server	Not available in Community Edition	✓
CockroachDB	–	–
CrateDB	–	–
CrateDB (Legacy)	–	–
Dameng	–	–
Data Virtuality	–	–
Db2 for IBM i	✓	–
Db2 for LUW	–	–
Db2 for z/OS	✓	–
Denodo 8	–	–
Derby Embedded	–	–
Derby Server	–	–
Dremio	–	–
DuckDB	–	–
EDB	✓	–
Exasol	✓	–
Firebird	✓	–
Fujitsu Enterprise Postgres	Not available in Community Edition	–
GaussDB	–	–
Google AlloyDB	Not available in Community Edition	✓
Google Cloud Spanner	✓	✓
Greenplum	✓	–
H2 Embedded	✓	–
H2 Embedded V.2	–	–
H2 Server	✓	–
H2GIS Embedded	–	–
H2GIS Server	–	–
HANA	✓	–
HSQL Embedded	–	–
HSQL Server	–	–
Informix	✓	–
Ingres	–	–
InterSystems IRIS	–	–
JDBCX	–	–
Jennifer	–	–
Kognitio	–	–
MS Access (UCanAccess)	–	–
MariaDB	✓	–
Materialize	–	–
MaxDB	–	–
Mimer SQL	–	–
MonetDB	–	–
MySQL	✓	✓
MySQL 5 (Legacy)	✓	–
NDB Cluster	–	–
NetSuite	Not available in Community Edition	–
Netezza	✓	–
NuoDB	–	–
ODBC	Not available in Community Edition	–
OceanBase	–	–
Ocient	–	–
OmniSci (formerly MapD)	–	–
OpenEdge	–	–
OpenSearch	✓	–
Oracle	✓	✓
Pervasive SQL	–	–
PostgreSQL	✓	✓
PrestoDB	–	–
PrestoSQL	–	–
Raima	Not available in Community Edition	–
Redshift	✓	✓
RisingWave	–	–
SAP ASE jConnect	–	–
SQL Server	✓	✓
SQL Server (Old driver, jTDS)	✓	–
SQLite	✓	–
SQLite Crypt	Not available in Community Edition	–
SQream DB	–	–
Salesforce	Not available in Community Edition	–
Salesforce Data Cloud	–	–
SingleStore	✓	–
Snowflake	✓	–
StarRocks	–	–
Sybase jConnect	✓	–
Sybase jTDS	✓	–
Teradata	✓	–
TiDB	–	–
Trino	–	–
Vertica	✓	–
Virtuoso	–	–
Yellowbrick	–	–
YugabyteDB	–	–

Non-Relational databases

Database name	Enhanced features* compared to the Community Edition	Available through Cloud Explorer
Apache Drill	✓	–
Apache Hive	✓	–
Apache Ignite	–	–
Apache Kyuubi	–	–
Apache Phoenix	–	–
Apache Spark	–	–
Athena	✓	✓
Cassandra	Not available in Community Edition	–
Cloudera Impala	–	–
CosmosDB (Cassandra)	Not available in Community Edition	✓
CosmosDB (MongoDB)	Not available in Community Edition	✓
CouchDB	Not available in Community Edition	–
Couchbase	Not available in Community Edition	–
Couchbase 5+	Not available in Community Edition	–
CSV	+	–
DBF	–	–
DocumentDB	Not available in Community Edition	✓
DynamoDB	Not available in Community Edition	✓
Elasticsearch	✓	–
Firestore	Not available in Community Edition	✓
Gemfire XD	–	–
Google BigQuery	✓	✓
Google Cloud Bigtable	Not available in Community Edition	✓
InfluxDB	Not available in Community Edition	–
InfluxDB 2	Not available in Community Edition	–
InfluxDB 3	Not available in Community Edition	–
Kafka (ksqlDB)	Not available in Community Edition	–
Keyspaces	Not available in Community Edition	✓
Machbase	–	–
MongoDB	Not available in Community Edition	–
Neo4j	✓	–
Neptune	Not available in Community Edition	✓
Open Distro Elasticsearch	✓	–
OrientDB	–	–
Parquet	Not available in Community Edition	–
Redis	Not available in Community Edition	–
ScyllaDB	Not available in Community Edition	–
SnappyData	–	–
Solr	–	–
TDengine	✓	–
TDengine Cloud	✓	–
TimescaleDB	–	–
Timestream	Not available in Community Edition	✓
XLSX	Not available in Community Edition	–
Yugabyte CQL	Not available in Community Edition	–

DBeaver uses tycho-surefire to run JUnit tests in the OSGi environment. This fact may slightly complicate the process of writing and running unit tests for DBeaver. Let’s take a look at possible ways to do that.

Using UNIX shell

Suppose we introduced some changes to our code and want to run the tests. It is actually quite easy:

$ cd /path/to/project/

$ mvn clean install

This compiles the project and runs unit tests.

If we only want to run unit tests:

$ cd test

$ mvn clean verify

The unit tests are separated into bundles. If you only want to run tests from a specific bundle, navigate to that bundle and run

there.

It is also worth pointing out that you need to recompile the whole project with

after every change in the project’s codebase before running unit tests, otherwise, you will be running tests against the previous version and it may lead to all sorts of confusion.

The interface themes governs the look and feel of the user interface’s windows, dialogs, buttons, and all other visual components. By default, DBeaver is configured to use the Light theme.

Change the DBeaver theme

1) Go to Window -> Preferences -> User Interface -> Appearance.

2) Select from the following available themes:

• Light
• Dark
• Classic

Note: To fully apply the selected theme, you must restart DBeaver.

Managing the High Contrast theme in Windows

Windows users have the additional option of using High Contrast themes. This section provides details on how DBeaver interacts with these themes.

Activation of High Contrast theme

When the High Contrast theme is activated in Windows, DBeaver automatically switches its theme to High Contrast. If DBeaver is already running when the system theme changes, a notification will appear suggesting a restart for the theme to apply correctly.

Deactivation of High Contrast theme

If you deactivate the High Contrast theme in Windows, it will automatically be removed from DBeaver’s list of available themes after the restart.

Note: After disabling the High Contrast theme in Windows, DBeaver will revert to the theme that was previously selected.

High Contrast theme switching limitations

The theme switcher in DBeaver is disabled when the High Contrast theme is active in Windows. You cannot switch to a non-High Contrast theme in DBeaver unless you disable the High Contrast theme in Windows.