Subject RE: [firebird-support] Traps using Local Filesystem Connect instead of TCP/IP
Author Alan McDonald
> On the weekend, I tried doing a local filesystem connect to a database,
> instead of via tcp/ip
>
> Via TCP/IP
> $conn = ibase_connect("localhost:/u1/db/data.fdb","sysdba","masterkey");
> Via Local (Process run as root)
> $conn = ibase_connect("/u1/db/data.fdb","sysdba","masterkey");

PHP?? right?
if you want this to run under Apache, then it's likely the threading of
Apache will try to make a separate connection for the next user and then
bang.. it will be locked out.
If this is a standalone PHP script, then you are under better control of
this aspect.
Alan

>
> The performance jump was incredible. It was easily 10x faster. As
> expected,
> the Firebird engine was pulled into the running application, rather than
> launching an 'fb_inet_server' process.
>
> Apart from the one drawback(I can see) of the process locking the database
> file, therefore locking all others (including 'fb_inet_server') out of the
> file (well, at least, it can't do anything until the first process is
> finished), are there any other traps, gotchas, or things to watch out for?
>
> Sorry this is a weirdly crafted question.
>
> N.
>
> Nigel Weeks