Subject | Re: [IB-Architect] Opening remote databases |
---|---|
Author | Ann Harrison |
Post date | 2000-08-25T14:16:10Z |
At 08:11 AM 8/25/00 +0000, jason.butlin@... wrote:
is correct. The reason for not opening a database on a remote disk
is that we can't know whether the database is already open elsewhere.
That's true in the "classic" architecture because each attachment
opens the database file, so file sharing is essential. In the
superserver, we may be able to fudge that rule.
Best,
Ann
InterBase is a registered trademark of Inprise Corporation.
>Currently, when you request to open a database on a remote drive,Alisdair M responded:
>Interbase will attempt to open it through an Interbase Server running
>on the remote machine. If no server is running, then Interbase will
>not open the database.
>
>However, in our use of Interbase it may be necessary to open a
>database that is hosted on a remote machine that doesn't have an
>Interbase server running.
>
>... It would also help solve our problem of storing the
>Interbase database on a Novell server, until the Netware port of
>Interbase comes out.
> Not just the network going down, what happens when 2 users try to openIt's a classic problem with all databases, I would think. Alisdair
> the same database file? This is the classic problem of desktop
> databases.
is correct. The reason for not opening a database on a remote disk
is that we can't know whether the database is already open elsewhere.
That's true in the "classic" architecture because each attachment
opens the database file, so file sharing is essential. In the
superserver, we may be able to fudge that rule.
Best,
Ann
InterBase is a registered trademark of Inprise Corporation.