You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this alias does not work with isql
e:\db.fdb=/db/db.fdb
this alias works fine with isql
e:/db.fdb=/db/db.fdb
aditional Infos from Alex Peshkoff:
This is a bug in aliases parser - slash is replaced to OS-specific slash in alias to resolve,
but not replaced in an alias read from aliases.conf. I.e. if you write
e/db.fdb=/db/db.fdb
both e/db.fdb & e\db.fdb will work from isql
based on my tests, using / in alias definitions can really be used as \ from commandline,
but isql for example on linux needs " around connection string
Need in quotes on linux when backslash (\) is used is not firebird but OS feature - shell tries to parse \+char sequences itself and isql receives the result of it, i.e.
localhost bin # echo "127.0.0.1:e:\db.fdb"
127.0.0.1:e:\db.fdb
localhost bin # echo 127.0.0.1:e:\db.fdb
127.0.0.1:e:db.fdb
Submitted by: Holger Klemt (klemmo)
a backslash in alias seems to be a problem,
this alias does not work with isql
e:\db.fdb=/db/db.fdb
this alias works fine with isql
e:/db.fdb=/db/db.fdb
aditional Infos from Alex Peshkoff:
This is a bug in aliases parser - slash is replaced to OS-specific slash in alias to resolve,
but not replaced in an alias read from aliases.conf. I.e. if you write
e/db.fdb=/db/db.fdb
both e/db.fdb & e\db.fdb will work from isql
based on my tests, using / in alias definitions can really be used as \ from commandline,
but isql for example on linux needs " around connection string
Entry in aliases.conf
e:/db.fdb=/db/db.fdb
succcessful connections:
root@IFS01:/opt/firebird/bin# ./isql "127.0.0.1:e/db.fdb" -user SYSDBA -password masterkey
Database: 127.0.0.1:e/db.fdb, User: SYSDBA
SQL> exit;
root@IFS01:/opt/firebird/bin# ./isql "127.0.0.1:e:\db.fdb" -user SYSDBA -password masterkey
Database: 127.0.0.1:e:\db.fdb, User: SYSDBA
SQL>
Commits: b690f21 6f5be2f c7423fd
The text was updated successfully, but these errors were encountered: