Issue Details (XML | Word | Printable)

Key: CORE-1905
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Claudio Valderrama C.
Reporter: Stefan Heymann
Votes: 0
Watchers: 1

If you were logged in you would be able to see more operations.
Firebird Core

Hash sign (#) in filenames in aliases.conf not handled correctly

Created: 18/May/08 05:00 AM   Updated: 19/Jan/16 04:57 AM
Component/s: Engine
Affects Version/s: 1.5.5, 2.1.0
Fix Version/s: 2.5 Alpha 1

Environment: Windows XP SP2

QA Status: No test

 Description  « Hide
For whatever reason, a customer wanted to have his database in a directory which contained a Hash character (#) in its name.

So the entry in aliases.conf looked like this

mydb = D:\#kit\subdir\mydatabase.fdb

The hash sign, however, starts a comment in aliases.conf. We could only work around that by selecting another directory (which can be
difficult when you have fixed naming conventions on a customer server).

Quoting the database filename doesn't help in Firebird 1.5.5. It just changes the error message when you try to create that database.

I also did a test with Firebird 2.1 with a quoted filename:

mydb = "D:\#kit\subdir\mydatabase.fdb"

With the above alias string, when I do a CREATE DATABASE, a file named MYDB (the name of the alias, without any extension) is created in the Firebird\bin (!) directory.

So there seems to be a problem with hash signs in alias filenames. I know this seems to be a rare case, but you can never know what crazy path naming conventions you find on customer's systems ...

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Claudio Valderrama C. added a comment - 19/May/08 03:41 AM
I will try to fix the logic only for aliases.conf

Dmitry Yemanov added a comment - 19/May/08 03:55 AM
IMHO, the correct solution would be to add support for double quotes in the right (value) part and treat the quoted string as a single entity.

Stefan Heymann added a comment - 19/May/08 04:04 AM
There already seems to be a kind of double quote support as Firebird 2.1 behaves differently than 1.5.