Subject Re: [firebird-support] Re: Remote Database files
Author Helen Borrie
At 08:12 AM 16/11/2005 +0000, you wrote:

># ----------------------------
># Remove protection against opening databases on NFS mounted volumes

But this refers to RemoteFileOpenAbility, not ExternalFileAccess!! (which
has to do with external data files that can be declared internally as
database tables, totally unrelated to this issue!

RemoteFileOpenAbility refers to the Unix Network File System, not Windows
networking. Unlike Windows, Unix doesn't have "disks", just file-like
devices. RemoteFileOpenAbility was never a good idea, even on
Unix; although could be OK for mounting a read-only database for some purpose.

># ***WARNING*** ***WARNING*** ***WARNING*** ***WARNING***
># This option removes an important safety feature of Firebird and can
># cause irrecoverable database corruption. Do not use this option
># you understand the risks and are prepared to accept the loss of the
># contents of your database.

What this means in plain English is that, if you want to do something this
silly, go ahead. It will work on Linux, etc.

># Unless this configuration option is changed from 0 to 1, Firebird
># open a database only if the database is stored on a drive
># attached to the local computer â€" the computer running that copy of
># Firebird. Requests for connections to databases stored on NFS
># drives are redirected to a Firebird server running on the computer
># "owns" the disk.
>"Unless this configuration option is changed from 0 to 1", means that
>if changed to 1, the option should allow Firebird to "open a database
>EVEN if the database is NOT stored on a drive physically
>attached to the local computer"...

But not on Windows.

>Am I getting this wrong?? Ok, I read all the warnings and I know what
>the risks are.. I'll try to avoid this situation and use local DB
>files. But, is this possible at all or the setting above is related
>to something else?
>If this is, however, possible what connection string should I use?

*If* your database server is hosted on Linux, then the connection string is
just like any connection string on Linux: it refers to the hostname that
is running the server and points to the NFS path. An NFS path is no
different to a local file system path on ***x.


You would use this path even if your clients were running on Windows.