Subject | Re: Possible to create DB using an alias? |
---|---|
Author | cwbauer2003 |
Post date | 2004-05-03T21:58:25Z |
Helen: Thanks for the quick response. I was afraid that would be the
answer although there are a couple of other replies to the contrary.
Security is not much of an issue in this application but come to think
of it, in general the aliases.conf file would not be accesable to the
user so extracting the path from that would not work.
Chuck
PS. Awaiting your book, I (and probably a few thousand others) really
need it.
PPS: Had some problem with reply to your reply. Maybe don't have the
hang of Mozilla yet. Sorry for delay.
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:
answer although there are a couple of other replies to the contrary.
Security is not much of an issue in this application but come to think
of it, in general the aliases.conf file would not be accesable to the
user so extracting the path from that would not work.
Chuck
PS. Awaiting your book, I (and probably a few thousand others) really
need it.
PPS: Had some problem with reply to your reply. Maybe don't have the
hang of Mozilla yet. Sorry for delay.
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:
> At 04:36 PM 2/05/2004 -0400, you wrote:accessing a
> >I'm trying to create a DB with FB1.5 (released) using an alias. The
> >alias points to where I want the DB created including its name which
> >works fine to connect to an existing DB. But trying to create one
> >programatically gives error 335544375, unavailable database. Not too
> >surprising since it of course does not yet exist. Is there a way to do
> >it short of reading the aliases.conf file, extracting the path and
> >creating a CREATE DATABASE statement with it?
>
> AFAIK, no. CREATE DATABASE has to have a hard path. It's a "bootstrap"
> problem, isn't it? I recall a discussion about on devel about possible
> logic but there are security considerations, too, of course. The main
> purpose of aliasing is to keep the hard path off the wire when
> database. It would be pretty futile if application code had someway to
> extract the alias path, wouldn't it? OTOH, it's up to the developer to
> decide how safe it is to create databases from remote applications.
>
> /heLen