Message-ID: <gh-pgjdbc-pgjdbc-2694-c2672491944@github.com>
From: "fladi (@fladi)" <noreply+fladi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 20 Feb 2025 19:34:55 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #2694: the url is invalid
In-Reply-To: <gh-pgjdbc-pgjdbc-2694@github.com>
References: <gh-pgjdbc-pgjdbc-2694@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: fladi
X-GitHub-Comment-Id: 2672491944
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 2694
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/2694#issuecomment-2672491944
Content-Type: text/plain; charset=utf-8

You are right, I created a new Connection in DBeaver using `%2f` and now it worked. For my first attempt I created a connection with `/` in the DB name and only changed it to `%2f` once I saw the remark in the documentation. So it is more of a DBeaver issue that it kept the original DB name somewhere.