RE: [Firebird-devel] Re: Y-valve & aliases

[Leyne, S. <sl...@at...>]

All,

In reading Jim's last message, a couple of things hit me and it has
prompted me to question the whole alias problem and has prompted some
questions.

First, it struck me: We have been talking/I have been thinking about
aliases only in the context of applications connecting to the database
(which is the most common need), but what about alias support for other
utilities/functions like GBAK, GFIX, etc???  So my question, do we
*need* to support aliases in the utilities?

Also, with respect to the suggestion which Ann made (quoted in Jim's
posting) that a new option be added to the IBConfig file (AliasOnly = 1)
to determine whether only aliases connections are allowed (with the
expection of user = SYSDBA who should always be able to connect).  Can
anybody come up with a case for only requiring aliases "sometimes"?

Jim and John Bellardo both mentioned user and system alias tables.  Can
somebody put forward a case for supporting user alias table?

Finally, I'm curious -- Does anyone think that they would actual *use*
client side aliases?


Now some technical questions:

Does the Y-Valve running on a server, know that it is running on the
server?

Also, if I specify a connection string of
"Server:Drive:\Path\database.gdb", by the time is reaches the remote
Y-Valve is it still "Server:Drive:\Path\database.gdb" or just
"Drive:\Path\database.gdb"?


Sean