[fpc-pascal] Re: linux: shouldwehard-codeversionedorunversionedshared libraries in our apps?

Reinier Olislagers reinierolislagers at gmail.com
Thu Aug 16 23:25:43 CEST 2012

On 16-8-2012 23:05, Graeme Geldenhuys wrote:
> On 16 August 2012 18:41, Michael Van Canneyt <michael-y8GAwIkqPAJpn7uciFS/BA at public.gmane.org> wrote:
>> Potential trouble ? After we have been loading it for the past 10 years ?
>> Let's not get carried away...
> I simply meant Firebird DB v3 has been in development for ages so
> could be released around the corner. It will be a major version
> change, so there is every chance that the API could change - though
> the Firebird project has been pretty good at not doing that. Anyway,
> at some point libfbclient.so could point to a v3 library, and all our
> apps are coded for a v2 library. That's all I meant. But thanks again
> for being understand.

Presumably the sqldb would be changed for the v3 library then?

Regardless, as mentioned, the Firebird services API allows you to find
out what version a server is running.
You can apparently find out what client lib is loaded.
Together, this info should be enough to modify sqldb to not issue
unsupported calls (i.e. use only those supported by the lowest
denominator). In other words: I'd rather build intelligence into the
driver code about what should work or shouldn't work.

In any case apparently that hasn't been a big problem up to now with
Interbase 6-whatever they've got now and
Firebird 1-2.5

More information about the fpc-pascal mailing list