Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104877
MIME-Version: 1.0
References: <CAJW__o1hA1DOp4Lf0LA2To5L-8c66+woFgoXAwfLaxxOiEwOPg@mail.gmail.com>
 <95e918c8-aaeb-d700-cc08-30f10a07162d@lsces.co.uk>
In-Reply-To: <95e918c8-aaeb-d700-cc08-30f10a07162d@lsces.co.uk>
Date: Fri, 22 Mar 2019 17:25:56 +0100
Message-ID: <CAF+90c_OGVmhiDRAqbd+X+9Ke0MMA9y0tsGRSo2_vRDPu87hPQ@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003ad94d0584b1508f"
Subject: Re: [PHP-DEV] [RFC] Unbundle ext/interbase
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000003ad94d0584b1508f
Content-Type: text/plain; charset="UTF-8"

On Fri, Mar 22, 2019 at 3:10 PM Lester Caine <lester@lsces.co.uk> wrote:

> On 22/03/2019 13:26, Kalle Sommer Nielsen wrote:
> > G'day internals
> >
> > I'd like to start the discussion for the future of the ext/interbase
> extension:
> > https://wiki.php.net/rfc/deprecate-and-remove-ext-interbase
> >
> > The rationale for pushing this extension out of the core is mentioned
> > in the RFC.
> >
> > Unless there is any serious issues raised here, then I will put this
> > into voting on Monday 8th of April, noon EET (which is a good two and
> > a half weeks away). The intended voting period is set for 2 weeks,
> > meaning if voting proceeds, the pools will be closed around Monday
> > 22th of April, noon EET.
>
> It is not that we don't want to stand up and maintain it, it has been
> impossible in recent years to get a handle on just what needs to be done
> TO maintain it. The PDO extension is in a much worse state than the main
> interbase one but both of them do their jobs as well as they can given
> that in the case of PDO it can't handle the cross database transactions,
> something that the main extension does quite happily.
>
> Personally I've been wasting time recently trying to keep alive sites
> that are using MySQL and the main problem with MySQL is the one thing
> that Firebird does nicely. Backup just runs as a secondary cron job
> independent of PHP while MySQL is reliant on PHP and current backups on
> some wordpress powered sites are failing because they run out of time or
> memory. I've never had a problem with loosing data with Firebird while
> I've had recover MySQL situations a few times in the last year!
>
> So all we are asking for is HELP with the code changes that result from
> changes to the PHP API to keep this available.
>

Hi Lester,

I've created a patch for https://bugs.php.net/bug.php?id=72175 (last
comment), which seems to be the biggest open problem in the interbase
extension. I'd appreciate it if you or someone else who uses firebird could
test this.

Nikita

--0000000000003ad94d0584b1508f--