Subject | Re: [Firebird-Architect] Database Capabilities |
---|---|
Author | Jim Starkey |
Post date | 2005-07-22T11:27:22Z |
Dmitry Sibiryakov wrote:
before anything could happen. And if you liked what you saw, you would
then have to reconnect with a proper password. That's two trips through
the connection code, potentially two database startups for what
benefit? A security liability?
The cost of capabilities + attach is much greater than attach +
capabilities, which is the standard case.
> I think this idea is not good enough. To obtain a database info youYou obviously have to connect to the database with a connection string
>must be connected to a database first. Personally, I'd like to be
>able to get engine capabilities before connecting or creating
>database.
>
before anything could happen. And if you liked what you saw, you would
then have to reconnect with a proper password. That's two trips through
the connection code, potentially two database startups for what
benefit? A security liability?
The cost of capabilities + attach is much greater than attach +
capabilities, which is the standard case.