Hi
Can there be any problem with a database, accessed simultaneously by
some or all of the following methods:
-- database file full path, /srv/firebird/mydb.fdb
-- database alias, mydb = /srv/firebird/mydb.fdb
-- another alias, another = /srv/firebird/mydb.fdb
-- /srv/firebird/link, which is a sy
I will have to install firebird 2.1 (preferably latest 2.1.7) on
64-bit RHEL/CentOS 6 based linux. (I understand 2.1 is discontinued,
but some program vendors don't).
The rpm and tar.gz packages from firebird.sql seem to fail [at least]
because of libstdc++ - if I understand correctly, they need
l
I feel it would be nice if in some highly visible place on the
firebird site there is a clear statement about the versions and
sub-versions available and recommended. Like they have it at
http://httpd.apache.org/:
"This latest release from the 2.4.x stable branch represents the best
available versi
Hi
As far as I understand, the Firebird 3 LINGER value is actually a property
of the database (file). How can I check if this is set and to what? I
thought GSTAT -h might show it, but it doesn't.
Regards
Emil
In Firebird 3.0.3 the current role is not passed to the external data
source when using 'execute statement ... on external'. This has been
acknowledged as a bug and fixed for 2.5.3 (see
http://tracker.firebirdsql.org/browse/CORE-4054)
However there is a note in the tracker saying "FB3 will have di
I ran into problems after upgrade from 2.5.7 to 2.5.8 (using the EPEL
repository, firebird-superserver). The server returns an error when trying
to access WIN1251 character fields, and there are log entries "Can't load
INTL module '/usr/lib64/firebird/intl/fbintl.so'" at server startup. (there
is r
XNET is not mentioned in the firebird.conf comments on IpcName, nor IpcName
is mentioned in README,xnet. Still I believe the two are connected. Am I
wrong?
With multiple Firebird installation on Windows it is necessary to change
the IpcName in each firebird.conf, but it seems only the one with the
This is a known problem with the EPEL rpms.
Workarounds include using the rpm packages for superclassic, which don't
have the problem, or installing the project-provided rpms (which install
under /opt). It *might* also work if you replace that specific file with
the one from the EPEL rpm from 2.5.7
