Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:104907 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 35087 invoked from network); 24 Mar 2019 00:49:01 -0000 Received: from unknown (HELO mail4.serversure.net) (185.153.204.204) by pb1.pair.com with SMTP; 24 Mar 2019 00:49:01 -0000 Received: (qmail 18295 invoked by uid 89); 23 Mar 2019 21:41:44 -0000 Received: by simscan 1.3.1 ppid: 18288, pid: 18292, t: 0.0491s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.7?) (lester@lsces.co.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 23 Mar 2019 21:41:44 -0000 To: Internals References: <33dee569-a06f-c5ab-d358-f7b8df3f8a76@lsces.co.uk> Message-ID: <1166897a-379d-4e6f-d132-744171ea19d5@lsces.co.uk> Date: Sat, 23 Mar 2019 21:41:43 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Unbundle ext/interbase From: lester@lsces.co.uk (Lester Caine) 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