mirror of
https://github.com/FirebirdSQL/firebird.git
synced 2025-01-22 18:03:03 +01:00
95 lines
3.2 KiB
Plaintext
95 lines
3.2 KiB
Plaintext
-----------------------------------------------------------
|
|
Firebird 1.5 Embedded Server notes
|
|
-----------------------------------------------------------
|
|
|
|
1. GENERIC INFORMATION
|
|
|
|
The embedded server is a fully functional server linked
|
|
as a dynamic library (fbembed.dll). It has exactly the
|
|
same features as the usual server and exports the
|
|
standard Firebird API entrypoints.
|
|
|
|
2. ISSUES AND LIMITATIONS
|
|
|
|
2.1. Registry
|
|
|
|
The Firebird registry entries are ignored. The root
|
|
directory of the embedded server is the directory of
|
|
its binary file (library).
|
|
|
|
2.2. Database access
|
|
|
|
The embedded server can act as a true local server
|
|
accessing databases on a local machine, and as a remote
|
|
gateway which redirects all network calls to another
|
|
hosts (i.e. works as a client library). Note that you
|
|
cannot connect to the local standalone Firebird server
|
|
using the local connection string (without a host name).
|
|
It applies to IPC connections only, because they use
|
|
the same format of the connection string; but you can
|
|
connect to the local standalone server via TCP/IP localhost
|
|
loopback or via the named pipes protocol.
|
|
|
|
2.3. Authentication and security
|
|
|
|
The security database (namely security.fdb) is not used
|
|
in the embedded server and hence is not required. Any
|
|
user is able to attach to any database. Since both
|
|
the server and the client run in the same address space,
|
|
the security becomes just an agreement between both
|
|
sides which can be easily compromised.
|
|
|
|
But note that SQL privileges are still checked.
|
|
|
|
2.4. Compatibility
|
|
|
|
You may run any number of applications with the embedded
|
|
server without any conflicts. Having IB/FB server running
|
|
is not a problem either.
|
|
|
|
But you should be aware that you cannot access single
|
|
database from a number of the embedded servers
|
|
simultaneously, because they have SuperServer architecture
|
|
and hence exclusively lock attached databases.
|
|
|
|
3. USAGE
|
|
|
|
Just copy fbembed.dll into the directory with your
|
|
application. Then rename it to either fbclient.dll or
|
|
gds32.dll depending on your database connectivity software.
|
|
Then start your application and it will use the embedded
|
|
server as a client library and will be able to access
|
|
local datasases. You should also copy firebird.msg and
|
|
firebird.conf (if necessary) to the same directory.
|
|
|
|
If external libraries are required for your application,
|
|
then you should have them separately. Most probably, it
|
|
will be INTL support (fbintl.dll) or UDF libraries. To
|
|
be able to use them, you should place them into the
|
|
directory tree which emulates the Firebird server one,
|
|
i.e. has subdirectories like /intl or /udf:
|
|
|
|
c:\my_app\app.exe
|
|
c:\my_app\gds32.dll
|
|
c:\my_app\ib_util.dll
|
|
c:\my_app\firebird.conf
|
|
c:\my_app\firebird.msg
|
|
c:\my_app\intl\fbintl.dll
|
|
c:\my_app\udf\fbudf.dll
|
|
|
|
If you want to place the Firebird files (excluding the
|
|
renamed fbembed.dll) in another directory, you need to
|
|
modify your firebird.conf and set RootDirectory to the
|
|
Firebird directory tree. Example:
|
|
|
|
c:\my_app\app.exe
|
|
c:\my_app\gds32.dll
|
|
c:\my_app\ib_util.dll
|
|
c:\my_app\firebird.conf
|
|
d:\fb\firebird.msg
|
|
d:\fb\intl\fbintl.dll
|
|
d:\fb\udf\fbudf.dll
|
|
|
|
firebird.conf:
|
|
RootDirectory = d:\fb
|