Erik,

E> Anyway, it's not a big deal, but in interests of consistency with the
E> single user model, it seems to me that the embedded server should be
E> able to work more like a desktop database, and allow database files to
E> be stored anywhere.

just so you don't think you're crazy <g>, I for one second your opinion that the
filesystem abstraction should be usable without restrictions at least
by the embedded server. AFAIK Firebird does not skip the filesystem in
any case. The embedded server shouldn't care at all
about the location of the database file since it's the only process
using it. To guarantee this the embedded server exclusively locks the
file upon connect. BUT a file on a network drive cannot always be safely
locked, hence the worries Helen and others (including myself) will express.

I think a configuration setting surrounded by a BIG warning note would
be more than enough to let the embedded server open whatever file you
ask for. The warning note should, err, warn the user that this working
mode is suitable only for scenarios like the one you have depicted.
IOW, if it's been done for NFS, it can be done for Windows shares.

I wouldn't use it, though. :-)

Ciao
--
Nando mailto:nandod@...