Hi,
Is there a way to set the timeout on connect() in fdb, and later
operations? It seems to take a very long time to timeout if connecting
to an unreachable host - minutes!
Thanks
Hamish
Hi Pavel,
I tried changing /etc/firebird/2.5/firebird.conf (I'm on Debian) but it
did not have any effect.
It's a shame this can't be set by individual client applications which
may have different requirements.
Thanks
Hamish
On 01/07/14 19:01, Pavel Cisar pci...@ibphoenix.cz
I've just upgraded my Debian Linux system to the new release (stretch/9)
and now I'm getting the following error when accessing a db from Python,
using either fdb (1.6.1) or the old kinterbasdb (3.3.0).
Unable to determine field precison from system tables:
Dynamic SQL Error
SQL error code =
Hi,
I'm trying to run a continuous loop waiting for events to be emitted
from Firebird and acting on them.
However I'm occasionally getting an exception:
Traceback (most recent call last):
File "/srv/blah/report_results.py", line 81, in
loop_on_events(('result_changed',), handler)
Further to last week's email about looping on events, I restructured my
code and I no longer get exceptions.
However I believe there is a flaw in the design of fdb.EventConduit
meaning events can be lost.
wait() blocks on the internal threading.Event, then copies the event
count. It does not