Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client-side use of databases.conf doesn't support modern URLs as value of an alias #8302

Open
mrotteveel opened this issue Nov 2, 2024 · 0 comments

Comments

@mrotteveel
Copy link
Member

Client-side, it is possible to specify aliases that have a legacy connection URL as its value:

testdb = localhost:E:\DB\FB5\FB5TESTDATABASE.FDB
{
    AuthClient = Legacy_Auth
}

When connecting with testdb, it will connect to localhost:E:\DB\FB5\FB5TESTDATABASE.FDB (using the specified config). If you specify localhost:E:\DB\FB5\FB5TESTDATABASE.FDB, it will also use the specified config.

However, the value of the alias can not be a modern url:

testdb2 = inet://localhost/E:\DB\FB5\FB5TESTDATABASE.FDB
{
    AuthClient = Legacy_Auth
}

With this config, attempts to connect with testdb2 will fail with error

Statement failed, SQLSTATE = 08006
Unable to complete network request to host "inet".
-Failed to locate host machine.
-The specified name was not found in the hosts file or Domain Name Services.

And attempts to connect with inet://localhost/E:\DB\FB5\FB5TESTDATABASE.FDB will not apply the specified configuration.

Expected behaviour would be for it to work the same as when the alias value is a legacy URL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants