Subject | Database names |
---|---|
Author | Jim Starkey |
Post date | 2000-04-29T14:54:05Z |
At 01:23 AM 4/29/00 -0400, Claudio Valderrama C. wrote:
breaks the layering) to moved into one of several authentication
plug-ins.
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
>Yes. I would like to see isc4.gdb removed from the engine (where it
>Why this couldn't be achieved creating a new table inside isc4.gdb? Do you
>want to see this global db removed in the future and replaced totally by a
>per-db security table(s)?
>
breaks the layering) to moved into one of several authentication
plug-ins.
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