Subject | RE: [firebird-support] Architecture of Firebird |
---|---|
Author | Nick |
Post date | 2006-04-10T08:59:48Z |
-----Original Message-----
The server is a process on the system. And the database resides
somewhere on the hard-disk as a file.
You don't load a database-file into the server. So the server-
software doesn't know which databases are running. As long as the
server is running, you can access the fdb-files as database.
So you can run different databases on one instance of the server-
software. And in the server-software you don't have to setup
anything according to the databases.
correct to here
The username/password is for the server. How is this in the database
itself? You don't have a userlist on every database. Only in the
server.
it isn't, the server has a seperate database that is always present, that
stores usernames, passwords etc
[Non-text portions of this message have been removed]
The server is a process on the system. And the database resides
somewhere on the hard-disk as a file.
You don't load a database-file into the server. So the server-
software doesn't know which databases are running. As long as the
server is running, you can access the fdb-files as database.
So you can run different databases on one instance of the server-
software. And in the server-software you don't have to setup
anything according to the databases.
correct to here
The username/password is for the server. How is this in the database
itself? You don't have a userlist on every database. Only in the
server.
it isn't, the server has a seperate database that is always present, that
stores usernames, passwords etc
[Non-text portions of this message have been removed]