Subject RE: [IB-Architect] Database names
Author Leyne, Sean
The only thing I would change is the location for the alias information.

I would suggest using isc4.gdb for two reasons.

Keeping isc4.gdb would enable better backward compatibility for security
functions (would still be the default security mode), until developers
get a handle on your plug-in security API.

Using a 'standard' db file, would provide some basic protection to the
configuration information. Access to the alias tables should restricted


-----Original Message-----
From: Jim Starkey [mailto:jas@...]
Sent: Saturday, April 29, 2000 10:54 AM
Subject: [IB-Architect] Database names

At 01:23 AM 4/29/00 -0400, Claudio Valderrama C. wrote:
>Why this couldn't be achieved creating a new table inside isc4.gdb? Do
>want to see this global db removed in the future and replaced totally
by a
>per-db security table(s)?

Yes. I would like to see isc4.gdb removed from the engine (where it
breaks the layering) to moved into one of several authentication

The "right" place for the mapping between database names and
database filenames is the registry for Windows systems and a
file in either the Interbase install directory or possibly
/etc on Unix (suggestions solicited).

The logical translation point is the Y-valve (why.c). Among
the algorithms that could be used:

1. Assume a connect string is a name if it doesn't contain
a dot.

2. Try to translate the connect string, regardless. If it
doesn't match a name, assume it's a file.

My druthers would be to make database names case insensitive to
match SQL semantics. Thoughts?

Jim Starkey

Accurate impartial advice on everything from laptops to table saws.

To unsubscribe from this group, send an email to: