Subject Re: [firebird-support] Re: FireBird CS locking on FreeBSD?
Author Geoffrey M. Ongley
On Sat, 26 Jul 2003 12:11 am, Helen Borrie wrote:
> At 09:25 AM 26/07/2003 +0000, you wrote:
> >but I wonder if your current problems have anything to do
> >
> > > with having the wrong client library. Have you checked that?
> >
> >Well, being that the "real" client for this thing is actually the
> > software written by this company (which is how I noticed the problem, I
> > only verified it using the isql client), no I haven't sepcifically
> > checked that. I will opt for the native binary of 1.0.2 and let you know
> > how I go.
>
> Now you've got me baffled. How does the client application connect to the
> database if it doesn't use the client library?
>

Oh, I'm mot saying it doesn't use the client library, just saying it doesn't
use the isql client. Sorry that wasn't clear. I may of misinterpretted what
you said.

> > Oh I don't expect CS to behave the same as superserver at all, I used CS
> > on Win 32 (1.0.0.796-0) and CS on *nix when comparing.
>
> I think not. There isn't a 1.0.x Classic Server for Windows. You could
> not possibly have done a local connect to a Classic server on Windows.
>

Really? Thats a huge surprise to me, as the people who have supplied the
software assure me it won't work on SS but DO provide a Win32 executeable, so
it is in fact SS? I know their software works using the win 32 Firebird, so I
guess hence it must work with SS.

I'm sorry, as you can tell I am relatively new to firebird, and was unaware of
this. This furthers my interest as to why they have made many claims they
have about the use of a specific version of firebird. I thankyou for your
feedback on this.

> >My understanding, though new to firebird is that CS is very different to
> > SS
>
> There are certainly architectural differences, but the API is
> identical. My point was that, just because a local connection works a
> certain way on Windows but not on Linux, don't think there is something
> wrong with the Linux implementation. Local connect on Windoze is a
> platform-specific "fudge" that has the client and the server working in
> the same interprocess communication space. It's designed for one and only
> one connection. If you write applications that depend on multiple
> Windoze-local connections (which I know you're not going to) then expect
> major problems. This is client/server software that uses its own network
> layer to support multiple connections.
>

I believe the software written by this company depends on BDE to connect to
firebird over the network. don't quote me on that. Thanks for your comments
giving me a better understanding of the software, it has helped immensly.

-Geoff