starred/cloudbeaver
1
0
Fork 0
mirror of https://github.com/dbeaver/cloudbeaver.git synced 2026-04-25 21:56:01 +03:00
Code Issues 212 Projects Releases Packages Wiki Activity

[GH-ISSUE #215] Adding Drivers to Custom Dockerfile #58

New issue
Closed
opened 2026-03-07 20:44:18 +03:00 by kerem · 10 comments
kerem commented 2026-03-07 20:44:18 +03:00
Owner
Copy link

Originally created by @jefflester on GitHub (Nov 12, 2020).
Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/215

I am trying to add a driver to the CloudBeaver Docker container and am running into some issues. I believe this is similar to issue #208. Reading the Wiki, this was how I expected things would work from a Dockerfile perspective:

Dockerfile:

FROM dbeaver/cloudbeaver:1.2.0

ADD ./pom.xml server/drivers/prestosql/
ADD ./plugin.xml server/bundles/io.cloudbeaver.resources.drivers.base/

Driver pom.xml:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <artifactId>drivers.prestosql</artifactId>
    <version>1.0.0</version>
    <parent>
        <groupId>io.cloudbeaver</groupId>
        <artifactId>drivers</artifactId>
        <version>1.0.0</version>
        <relativePath>../</relativePath>
    </parent>
    <properties>
        <deps.output.dir>prestosql</deps.output.dir>
    </properties>
    <dependencies>
        <dependency>
            <groupId>io.prestosql</groupId>
            <artifactId>presto-jdbc</artifactId>
            <version>338</version>
        </dependency>
    </dependencies>
</project>

Plugin XML:

<!-- Bundles  -->
<extension point="org.jkiss.dbeaver.product.bundles">
    <bundle id="drivers.clickhouse" label="Clickhouse drivers"/>
    <bundle id="drivers.derby" label="Derby drivers"/>
    <bundle id="drivers.firebird" label="Firebird drivers"/>
    <bundle id="drivers.h2" label="H2 drivers"/>
    <bundle id="drivers.mysql" label="MySQL drivers"/>
    <bundle id="drivers.mariadb" label="MariaDB drivers"/>
    <bundle id="drivers.postgresql" label="PostgreSQL drivers"/>
    <bundle id="drivers.prestosql" label="PrestoSQL drivers"/>
    <bundle id="drivers.sqlite.xerial" label="SQLite drivers"/>
</extension>

<!-- Enabled drivers -->
<extension point="io.cloudbeaver.driver">
    <driver id="generic:yandex_clickhouse"/>
    <driver id="generic:derby_server"/>
    <driver id="jaybird:jaybird"/>
    <driver id="generic:h2_embedded"/>
    <driver id="mysql:mysql8"/>
    <driver id="mysql:mariaDB"/>
    <driver id="postgresql:postgres-jdbc"/>
    <driver id="generic:prestosql_jdbc"/>
    <driver id="generic:sqlite_jdbc"/>
</extension>
```

However, it appears these instructions expect the user to be building from source with the build.sh script after the relevant files have been updated/added. Going off that, it looks like the cloudbeaver source is added to the Docker image after the build.sh script is run, per the Dockerfile.

Is there an interim Maven command I need to add to the image entrypoint to get this to work? The default entrypoint ENTRYPOINT ["./run-server.sh"] does not register the added drivers since no build commands are executed.

Thanks for any and all clarification, and I am very excited to start using this! I'm happy to create a doc PR to update the instructions for adding drivers to a custom Dockerfile if that would be helpful as well.

Originally created by @jefflester on GitHub (Nov 12, 2020). Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/215 I am trying to add a driver to the CloudBeaver Docker container and am running into some issues. I believe this is similar to issue #208. Reading the [Wiki](https://github.com/dbeaver/cloudbeaver/wiki/Driver-managements), this was how I expected things would work from a Dockerfile perspective: Dockerfile: ``` FROM dbeaver/cloudbeaver:1.2.0 ADD ./pom.xml server/drivers/prestosql/ ADD ./plugin.xml server/bundles/io.cloudbeaver.resources.drivers.base/ ``` Driver `pom.xml`: ``` <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <artifactId>drivers.prestosql</artifactId> <version>1.0.0</version> <parent> <groupId>io.cloudbeaver</groupId> <artifactId>drivers</artifactId> <version>1.0.0</version> <relativePath>../</relativePath> </parent> <properties> <deps.output.dir>prestosql</deps.output.dir> </properties> <dependencies> <dependency> <groupId>io.prestosql</groupId> <artifactId>presto-jdbc</artifactId> <version>338</version> </dependency> </dependencies> </project> ``` Plugin XML: <?xml version="1.0" encoding="UTF-8"?> <plugin> <!-- Resource mappings --> <extension point="org.jkiss.dbeaver.resources"> <resource name="drivers/clickhouse"/> <resource name="drivers/derby"/> <resource name="drivers/jaybird"/> <resource name="drivers/h2"/> <resource name="drivers/mysql/mysql8"/> <resource name="drivers/mariadb"/> <resource name="drivers/postgresql"/> <resource name="drivers/prestosql"/> <resource name="drivers/sqlite/xerial"/> </extension> <!-- Bundles --> <extension point="org.jkiss.dbeaver.product.bundles"> <bundle id="drivers.clickhouse" label="Clickhouse drivers"/> <bundle id="drivers.derby" label="Derby drivers"/> <bundle id="drivers.firebird" label="Firebird drivers"/> <bundle id="drivers.h2" label="H2 drivers"/> <bundle id="drivers.mysql" label="MySQL drivers"/> <bundle id="drivers.mariadb" label="MariaDB drivers"/> <bundle id="drivers.postgresql" label="PostgreSQL drivers"/> <bundle id="drivers.prestosql" label="PrestoSQL drivers"/> <bundle id="drivers.sqlite.xerial" label="SQLite drivers"/> </extension> <!-- Enabled drivers --> <extension point="io.cloudbeaver.driver"> <driver id="generic:yandex_clickhouse"/> <driver id="generic:derby_server"/> <driver id="jaybird:jaybird"/> <driver id="generic:h2_embedded"/> <driver id="mysql:mysql8"/> <driver id="mysql:mariaDB"/> <driver id="postgresql:postgres-jdbc"/> <driver id="generic:prestosql_jdbc"/> <driver id="generic:sqlite_jdbc"/> </extension> </plugin> ``` However, it appears these instructions expect the user to be building from source with the `build.sh` script _after_ the relevant files have been updated/added. Going off that, it looks like the `cloudbeaver` source is added to the Docker image after the `build.sh` script is run, per the [Dockerfile](https://github.com/dbeaver/cloudbeaver/blob/devel/deploy/docker/Dockerfile#L6). Is there an interim Maven command I need to add to the image entrypoint to get this to work? The default entrypoint `ENTRYPOINT ["./run-server.sh"]` does not register the added drivers since no build commands are executed. Thanks for any and all clarification, and I am very excited to start using this! I'm happy to create a doc PR to update the instructions for adding drivers to a custom Dockerfile if that would be helpful as well.
kerem 2026-03-07 20:44:18 +03:00
kerem commented 2026-03-07 20:44:19 +03:00
Author
Owner
Copy link

@jefflester commented on GitHub (Nov 18, 2020):

I confirmed that the COPY cloudbeaver /opt/cloudbeaver Dockerfile instruction is grabbing the build artifacts resulting from build.sh script. So it does in fact appear that the only way to add drivers to your Dockerized CloudBeaver is to design your own Dockerfile and to copy over your own built distribution.

If I'm wrong and there's an easier way to do this, please let me know.

<!-- gh-comment-id:729961583 --> @jefflester commented on GitHub (Nov 18, 2020): I confirmed that the `COPY cloudbeaver /opt/cloudbeaver` Dockerfile instruction is grabbing the build artifacts resulting from `build.sh` script. So it does in fact appear that the only way to add drivers to your Dockerized CloudBeaver is to design your own Dockerfile and to copy over your own built distribution. If I'm wrong and there's an easier way to do this, please let me know.
kerem commented 2026-03-07 20:44:19 +03:00
Author
Owner
Copy link

@serge-rider commented on GitHub (Nov 19, 2020):

You don't need to change Dockerfile in order to add drivers. Dockerfile copies all drivers configured in pom.xml and pluginx.xml.
We plan to add Presto as pre-configured driver in the next version (1.3).

<!-- gh-comment-id:730226001 --> @serge-rider commented on GitHub (Nov 19, 2020): You don't need to change Dockerfile in order to add drivers. Dockerfile copies all drivers configured in pom.xml and pluginx.xml. We plan to add Presto as pre-configured driver in the next version (1.3).
kerem commented 2026-03-07 20:44:19 +03:00
Author
Owner
Copy link

@jefflester commented on GitHub (Nov 19, 2020):

Thanks for confirming, @serge-rider. A couple of quick followup questions:

  1. Do you plan to add PrestoSQL, PrestoDB, or both drivers in the 1.3 release?
  2. If you don't need to change/make your own Dockerfile, how do you actually add drivers to a container? I'm probably misunderstanding (if this is possible), but it looks like you need to clone the CloudBeaver source, add the new driver resources, build it, and then add the built distro to your own Dockerfile.

Thank you again! We're really excited to start using this. :)

<!-- gh-comment-id:730478753 --> @jefflester commented on GitHub (Nov 19, 2020): Thanks for confirming, @serge-rider. A couple of quick followup questions: 1. Do you plan to add PrestoSQL, PrestoDB, or both drivers in the 1.3 release? 2. If you don't need to change/make your own Dockerfile, how do you actually add drivers to a container? I'm probably misunderstanding (if this is possible), but it looks like you need to clone the CloudBeaver source, add the new driver resources, build it, and then add the built distro to your own Dockerfile. Thank you again! We're really excited to start using this. :)
kerem commented 2026-03-07 20:44:19 +03:00
Author
Owner
Copy link

@darint00 commented on GitHub (Nov 20, 2020):

Yes, please explain how to add a driver to the container. I have an Informix driver I'd like to add. And the only thing, as mentioned above, I can think of is ..

  1. Create your own image with a dockerfile that adds the specific driver you want.
    If there is another way, easier way, please let us know.
<!-- gh-comment-id:731381951 --> @darint00 commented on GitHub (Nov 20, 2020): Yes, please explain how to add a driver to the container. I have an Informix driver I'd like to add. And the only thing, as mentioned above, I can think of is .. 1. Create your own image with a dockerfile that adds the specific driver you want. If there is another way, easier way, please let us know.
kerem commented 2026-03-07 20:44:19 +03:00
Author
Owner
Copy link

@mskyttner commented on GitHub (Dec 16, 2020):

I too would like to add a driver but didn't figure it out.

This is a draft multi-stage Dockerfile that builds in the first step and then moves build results in the second step (probably some things are moved which doesn't need to be moved, I'm a bit unfamiliar with the build tools).

But where would I add my jdbc driver?

FROM adoptopenjdk/openjdk11:x86_64-ubuntu-jdk-11.0.7_10

RUN apt-get update -y && apt-get install -y \
	nano \
	git \
	maven

RUN apt-get install -y gnupg && curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - 

RUN echo "deb https://dl.yarnpkg.com/debian/ stable main" > /etc/apt/sources.list.d/yarn.list && \
	apt-get update -y && apt-get install -y --no-install-recommends \
	yarn

# build server
RUN mkdir conf workspace web
RUN git clone --depth=1 https://github.com/dbeaver/cloudbeaver.git
RUN git clone --depth=1 https://github.com/dbeaver/dbeaver.git

WORKDIR /cloudbeaver

RUN cd server/product/aggregate && \
	mvn clean package -Dheadless-platform

RUN cp -rp server/product/web-server/target/products/io.cloudbeaver.product/all/all/all/* server && \
	cp -p deploy/scripts/* .

RUN mkdir -p deploy/cloudbeaver/samples/db deploy/cloudbeaver/conf && \
	cp -rp samples/sample-databases/db deploy/cloudbeaver/samples/ && \
	cp -rp samples/sample-databases/GlobalConfiguration/.dbeaver/data-sources.json deploy/cloudbeaver/conf/initial-data-sources.conf && \
	cp -p samples/sample-databases/*.conf deploy/cloudbeaver/conf/ && \
	mv server/drivers deploy/cloudbeaver

# build frontend

RUN curl -sL https://deb.nodesource.com/setup_14.x -o nodesource_setup.sh && \
	chmod +x ./nodesource_setup.sh && ./nodesource_setup.sh && \
	apt-get install -y nodejs

RUN cd webapp && yarn && \
	yarn add -W lerna --dev && \
	npm install --global lerna && \
	lerna run build --stream --scope=@cloudbeaver/product-default -- -- --mode=production

RUN mkdir -p deploy/cloudbeaver/web && \
	cp -rp webapp/packages/product-default/lib/* deploy/cloudbeaver/web

RUN mv /cloudbeaver /opt/cloudbeaver

FROM adoptopenjdk/openjdk11:alpine-slim

COPY --from=0 /opt/cloudbeaver /opt/cloudbeaver

RUN apk --update --no-cache add tini bash

WORKDIR /opt/cloudbeaver

EXPOSE 8978
ENTRYPOINT ["/sbin/tini", "--"]
CMD ["/opt/cloudbeaver/run-server.sh"]
<!-- gh-comment-id:746694576 --> @mskyttner commented on GitHub (Dec 16, 2020): I too would like to add a driver but didn't figure it out. This is a draft multi-stage Dockerfile that builds in the first step and then moves build results in the second step (probably some things are moved which doesn't need to be moved, I'm a bit unfamiliar with the build tools). But where would I add my jdbc driver? ```Dockerfile FROM adoptopenjdk/openjdk11:x86_64-ubuntu-jdk-11.0.7_10 RUN apt-get update -y && apt-get install -y \ nano \ git \ maven RUN apt-get install -y gnupg && curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - RUN echo "deb https://dl.yarnpkg.com/debian/ stable main" > /etc/apt/sources.list.d/yarn.list && \ apt-get update -y && apt-get install -y --no-install-recommends \ yarn # build server RUN mkdir conf workspace web RUN git clone --depth=1 https://github.com/dbeaver/cloudbeaver.git RUN git clone --depth=1 https://github.com/dbeaver/dbeaver.git WORKDIR /cloudbeaver RUN cd server/product/aggregate && \ mvn clean package -Dheadless-platform RUN cp -rp server/product/web-server/target/products/io.cloudbeaver.product/all/all/all/* server && \ cp -p deploy/scripts/* . RUN mkdir -p deploy/cloudbeaver/samples/db deploy/cloudbeaver/conf && \ cp -rp samples/sample-databases/db deploy/cloudbeaver/samples/ && \ cp -rp samples/sample-databases/GlobalConfiguration/.dbeaver/data-sources.json deploy/cloudbeaver/conf/initial-data-sources.conf && \ cp -p samples/sample-databases/*.conf deploy/cloudbeaver/conf/ && \ mv server/drivers deploy/cloudbeaver # build frontend RUN curl -sL https://deb.nodesource.com/setup_14.x -o nodesource_setup.sh && \ chmod +x ./nodesource_setup.sh && ./nodesource_setup.sh && \ apt-get install -y nodejs RUN cd webapp && yarn && \ yarn add -W lerna --dev && \ npm install --global lerna && \ lerna run build --stream --scope=@cloudbeaver/product-default -- -- --mode=production RUN mkdir -p deploy/cloudbeaver/web && \ cp -rp webapp/packages/product-default/lib/* deploy/cloudbeaver/web RUN mv /cloudbeaver /opt/cloudbeaver FROM adoptopenjdk/openjdk11:alpine-slim COPY --from=0 /opt/cloudbeaver /opt/cloudbeaver RUN apk --update --no-cache add tini bash WORKDIR /opt/cloudbeaver EXPOSE 8978 ENTRYPOINT ["/sbin/tini", "--"] CMD ["/opt/cloudbeaver/run-server.sh"] ```
kerem commented 2026-03-07 20:44:19 +03:00
Author
Owner
Copy link

@momiji commented on GitHub (Jan 8, 2021):

does it help #259 ?

<!-- gh-comment-id:757041678 --> @momiji commented on GitHub (Jan 8, 2021): does it help #259 ?
kerem commented 2026-03-07 20:44:19 +03:00
Author
Owner
Copy link

@jefflester commented on GitHub (Jan 12, 2021):

does it help #259 ?

@momiji It adds some clarity––it looks like your flow involves cloning both DBeaver and Cloudbeaver, making adjustments to each repository, and then building them with the changes. Please correct me if I'm wrong.

I'm interested in using the provided Docker image and extending it through my own Dockerfile without the need to modify and build both the DBeaver and CloudBeaver repositories. If that's the required flow, I'll probably wait until release 1.3 comes out for native support of Presto JDBC drivers. Speaking of which, @serge-rider do you know if you're adding the Trino (formerly PrestoSQL) or the PrestoDB drivers?

In terms of adding new drivers to the Docker image, this is how I'd envision it working:

FROM dbeaver/cloudbeaver:1.2.0

ADD ./pom.xml server/drivers/prestosql/
ADD ./plugin.xml server/bundles/io.cloudbeaver.resources.drivers.base/

Or by simply mounting the files to the base CloudBeaver image without modifying it through a Dockefile at all.

Thanks again, everyone!

<!-- gh-comment-id:758768167 --> @jefflester commented on GitHub (Jan 12, 2021): > does it help #259 ? @momiji It adds some clarity––it looks like your flow involves cloning both DBeaver and Cloudbeaver, making adjustments to each repository, and then building them with the changes. Please correct me if I'm wrong. I'm interested in using the provided Docker image and extending it through my own Dockerfile without the need to modify and build both the DBeaver and CloudBeaver repositories. If that's the required flow, I'll probably wait until release 1.3 comes out for native support of Presto JDBC drivers. Speaking of which, @serge-rider do you know if you're adding the [Trino](https://github.com/trinodb/trino) (formerly PrestoSQL) or the PrestoDB drivers? In terms of adding new drivers to the Docker image, this is how I'd envision it working: ``` FROM dbeaver/cloudbeaver:1.2.0 ADD ./pom.xml server/drivers/prestosql/ ADD ./plugin.xml server/bundles/io.cloudbeaver.resources.drivers.base/ ``` Or by simply mounting the files to the base CloudBeaver image without modifying it through a Dockefile at all. Thanks again, everyone!
kerem commented 2026-03-07 20:44:20 +03:00
Author
Owner
Copy link

@momiji commented on GitHub (Jan 12, 2021):

Hi,

@momiji It adds some clarity––it looks like your flow involves cloning both DBeaver and Cloudbeaver, making adjustments to each repository, and then building them with the changes. Please correct me if I'm wrong.

Absolutely, you're right.

Concerning your idea ti build from docker image, what you're proposing cannot work, because adding the pom.xml is not for the single purpose of adding a new file on the filesystem, but to add a new sub-project in the project building process (which uses maven, which uses pom.xml...).

So my understanding is you definitely need to rebuild the project... Then, rebuilding one or two, no difference especially as the build.sh script rebuilds both...

Regards.

<!-- gh-comment-id:758867579 --> @momiji commented on GitHub (Jan 12, 2021): Hi, > @momiji It adds some clarity––it looks like your flow involves cloning both DBeaver and Cloudbeaver, making adjustments to each repository, and then building them with the changes. Please correct me if I'm wrong. Absolutely, you're right. Concerning your idea ti build from docker image, what you're proposing cannot work, because adding the pom.xml is not for the single purpose of adding a new file on the filesystem, but to add a new sub-project in the project building process (which uses maven, which uses pom.xml...). So my understanding is you definitely need to rebuild the project... Then, rebuilding one or two, no difference especially as the build.sh script rebuilds both... Regards.
kerem commented 2026-03-07 20:44:20 +03:00
Author
Owner
Copy link

@serge-rider commented on GitHub (Feb 1, 2021):

Please see instruction how to add new drivers: https://github.com/dbeaver/cloudbeaver/wiki/Adding-new-database-drivers

<!-- gh-comment-id:770885768 --> @serge-rider commented on GitHub (Feb 1, 2021): Please see instruction how to add new drivers: https://github.com/dbeaver/cloudbeaver/wiki/Adding-new-database-drivers
kerem commented 2026-03-07 20:44:20 +03:00
Author
Owner
Copy link

@kseniiaguzeeva commented on GitHub (Feb 11, 2021):

Please ask to reopen the ticket if you have some additional questions.

<!-- gh-comment-id:777305577 --> @kseniiaguzeeva commented on GitHub (Feb 11, 2021): Please ask to reopen the ticket if you have some additional questions.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
devel
dbeaver/cloudbeaver#4120-support-token-header
dbeaver/pro#8978-advanced-paste
dbeaver/pro#5680-add-generation-rest-api-for-te
8961-cb-checkboxes-are-not-clickable-in-main-toolbar-dropdown-menu
dbeaver/pro#9047-cb-explain-execution-plan-ai
8328-cb-sql-query-generation-add-settings-for-the-generated-sql-window
8473-ai-confirmation
8107-cb-increase-the-contrast-of-some-elements
dbeaver/cloudbeaver#4249-session-id-rotation
dbeaver/pro#8234-udbt-only-for-admins
dbeaver/pro#9061-NPE-on-starting-RM-and-QM-applications
dbeaver/pro#8707-remove-folder-feature
dbeaver/pro#8766-migrate-to-junit5
dbeaver/pro#8711-sql-executation-plan-improvments
9048-cb-deadlock
release_26_0_3
dbeaver/pro#8044-add-api-for-database-user-preference
8839-entraid-not-working-from-within-myappsmicrosoftcom
8559-te-launch-redesign
8670-cb-multi-paste-support-in-data-editor-3
8943-cb-bump-npm-dependencies
dbeaver/pro#8655-cb-ai-functions-support
dbeaver/pro#8746-oauth
dbeaver/pro#8824-Unify-file-lock-handling-for-local-and-shared-fs
7912-db-oauth-in-te
dbeaver/pro#4158-tree-advanced-filter
dbeaver/dbeaver-devops#1604-non-root-user-25-2
dbeaver/pro#5124-fix-case-insensetive-username-in-import
3815-ctrl-z-is-unstable-lib-523-version
8894-ai-assistant-cache
dbeaver/pro#8896-Remove-added-h2_server_v3
release_26_0_2
dbeaver/pro#8392-Add-H2-driver-with-the-newest-version
8065-lsp-front-end
release_26_0_1
dbeaver/pro#7844-cb-lsp-server
dbeaver/pro#7530-csp-protection
release_26_0_0
release_25_3_5
release_25_3_4
release_25_3_3
7953-cb-ability-to-pin-rows-in-the-data-editor
devops-2221-base-java-repo
7923-cb-ws-events-are-misconfigured
release_25_3_2
release_25_3_1
release_25_3_0
release_25_2_5
dbeaver/pro#5267/auth-providers-refactoring
dbeaver/pro#6364-add-option-to-set-default-view-for-project
release_25_2_4
dbeaver/pro#5476-task-scheduler-refactor
release_25_2_3
7128-remove-deprecated-api
release_25_2_0
release_25_2_1
release_25_2_2
4569-cb-3681-use-something-better-than-md5-hash-to-pass-local-user-passwords
dbeaver/dbeaver-devops#1604-non-root-user-without-user-in-image
dbeaver/pro#6976-logging-poc
dbeaver/pro#6324-cursor-sync
dbeaver/pro#5630-add-cache-for-queries
dbeaver/pro#5574/fix/multi-query-vqb
dbeaver/pro#5802/feat/table-api
5664-cb-vscode-value-panel-support-text-format
CB-6291-build-local-script-do-not-clone-all-required-repos-for-successful-build
4288-core-fix-critical-cve-2022-0839-and-cve-2022-0839-in-liquibase-bundle
3944-model-data
4207-core-duplicate-cb-session-id-in-dc-side
chore/update-vite-assets-plugin
25.1.5
25.1.4
25.1.3
25.1.2
25.1.1
25.1.0
25.0.5
25.0.4
25.0.3
25.0.2
25.0.1
25.0.0
24.3.5
24.3.4
24.3.3
24.3.2
24.3.0
24.3.1
24.2.5
24.2.4
24.2.3
24.2.2
24.2.1
24.2.0
24.1.5
24.1.4
24.1.3
24.1.2
24.1.0
24.1.1
24.0.5
24.0.4
24.0.3
24.0.2
24.0.1
24.0.0
23.3.5
23.3.4
23.3.3
23.3.2
23.3.1
23.3.0
23.2.5
23.2.4
23.2.3
23.2.2
23.2.1
23.2.0
23.1.5
23.1.4
23.1.3
23.1.2
23.1.1
v23.1.0
v23_0_5
21.3.3
21.2.4
1.2.0
1.1.0
1.0.4
1.0.3
1.0.1b
1.0.2
1.0.1
1.0.0
Labels
Clear labels   
AS

   
can't reproduce

   
can't reproduce

   
deployment

   
development

   
documentation

   
duplicate

   
duplicate

   
ee

   
enhancement

   
external

   
new driver

   
performance

   
pull-request

Mirrored from GitHub Pull Request

  
third party issue

   
wait for response

   
wait for review

   
wontfix

   
x:Oracle

   
x:cassandra

   
x:clickhouse

   
x:db2

   
x:duckdb

   
x:greenplum

   
x:h2

   
x:h2gis

   
x:hana

   
x:hive

   
x:intersystems

   
x:kyuubi

   
x:maria

   
x:mongo

   
x:mysql

   
x:postgresql

   
x:presto

   
x:sql server

   
x:sqlite

   
x:teradata

   
x:trino

   
xf:accessibility

   
xf:administration

   
xf:ai

   
xf:authentication

   
xf:aws

   
xf:commit-mode

   
xf:connection

   
xf:dark theme

   
xf:data editor

   
xf:datatransfer

   
xf:dba

   
xf:driver management

   
xf:erd

   
xf:filters

   
xf:i18n

   
xf:i18n

   
xf:installer

   
xf:json

   
xf:kerberos

   
xf:ldap

   
xf:local config

   
xf:log viewer

   
xf:metadata

   
xf:metadata editor

   
xf:navigator

   
xf:okta

   
xf:query manager

   
xf:resource manager

   
xf:scripts

   
xf:sql editor

   
xf:tasks

   
xf:ui/uix

   
xo: Firefox

   
xo:eclipse

   
xo:internet explorer

   
xo:macos

   
xp:major

   
xrn:internal
No labels
AS
can't reproduce
can't reproduce
deployment
development
documentation
duplicate
duplicate
ee
enhancement
external
new driver
performance
pull-request
third party issue
wait for response
wait for review
wontfix
x:Oracle
x:cassandra
x:clickhouse
x:db2
x:duckdb
x:greenplum
x:h2
x:h2gis
x:hana
x:hive
x:intersystems
x:kyuubi
x:maria
x:mongo
x:mysql
x:postgresql
x:presto
x:sql server
x:sqlite
x:teradata
x:trino
xf:accessibility
xf:administration
xf:ai
xf:authentication
xf:aws
xf:commit-mode
xf:connection
xf:dark theme
xf:data editor
xf:datatransfer
xf:dba
xf:driver management
xf:erd
xf:filters
xf:i18n
xf:i18n
xf:installer
xf:json
xf:kerberos
xf:ldap
xf:local config
xf:log viewer
xf:metadata
xf:metadata editor
xf:navigator
xf:okta
xf:query manager
xf:resource manager
xf:scripts
xf:sql editor
xf:tasks
xf:ui/uix
xo: Firefox
xo:eclipse
xo:internet explorer
xo:macos
xp:major
xrn:internal
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cloudbeaver#58
No description provided.