On 23/03/2019 21:09, Kalle Sommer Nielsen wrote:
I updated the RFC with a section earlier to list some of the issues
the extension currently has.
Thread safety is one area where the way the extension was structured
originally may now be wrong, but the main problem with multiple
connections is confined completely to multiple connections to a single
database. In particular the 'default link' is actually the default
transaction handle and additional links are simply multiple transactions
on the one connection which I think is where some of the confusion has
come from :( A more established Firebird user would simply start a new
transaction, while a newbie may try to start a new connection. And in
the past the extension has hidden that and quietly picked up the
existing one ...
"A small subset of field types are supported, anything else crashes"
This is news to me ... is there any bug report to back it up? All the
current data types provided by Firebird are working in the extension,
but you may well be right that we may be better off cloning the existing
code and building a Firebird only port going forward. The concern is the
same one we had with windows in the past, where adding extra extensions
does not always work reliably ... one has to provide a wrapped package
with all the edge cases addressed. But all my use in production is using
ADOdb to wrap the database SQL problems ...
--
Lester Caine - G8HFL
-----------------------------
Contact - https://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - https://lsces.co.uk
EnquirySolve - https://enquirysolve.com/
Model Engineers Digital Workshop - https://medw.co.uk
Rainbow Digital Media - https://rainbowdigitalmedia.co.uk
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
