Subject | Re: [ib-support] connecting to firebird |
---|---|
Author | Svein Erling Tysvaer |
Post date | 2003-03-12T08:57:44Z |
Leon,
if you are thinking about the bug where one connection had the backslash
and the other none (i.e. h:\database.gdb vs h:database.gdb), which made IB
think of them as two separate databases and thus corrupting the entire
database, then I think this bug has been fixed in Firebird. As for
InterBase I do not know, but a bug corrupting the database is so severe
that I'd be greatly surprised if they hadn't done anything about it (I know
that IBO was changed to not accept a connection without a backslash pretty
quickly after this error was discovered).
HTH,
Set
At 08:10 12.03.2003 +0000, you wrote:
if you are thinking about the bug where one connection had the backslash
and the other none (i.e. h:\database.gdb vs h:database.gdb), which made IB
think of them as two separate databases and thus corrupting the entire
database, then I think this bug has been fixed in Firebird. As for
InterBase I do not know, but a bug corrupting the database is so severe
that I'd be greatly surprised if they hadn't done anything about it (I know
that IBO was changed to not accept a connection without a backslash pretty
quickly after this error was discovered).
HTH,
Set
At 08:10 12.03.2003 +0000, you wrote:
>Hi,
>
>I think once there were possible corruption-problems in interbase if
>two clients connected to the same database using different ways.
>1. using the driveletter ( h:\database.gdb )
>2. using the servername
>3. using the IP-adress
>
>Is wonder if this is still the case ? My users are able to connect to
>a different database by browsing, and chances are really big that
>this will result in a different way of connecting to the same database