On 19.09.2018 at 19:57, BohwaZ wrote:
> On Wed, 19 Sep 2018 19:41:11 +0200 / "Christoph M. Becker"
> said :
>
>> PR #2698[2] seems to require an RFC. IMHO, it's best to present RFCs
>> and voting on them as early as possible (instead of rushing them at
>> the last moment). :)
>
> Yeah there
On Wed, 19 Sep 2018 19:41:11 +0200 / "Christoph M. Becker"
said :
> PR #2698[2] seems to require an RFC. IMHO, it's best to present RFCs
> and voting on them as early as possible (instead of rushing them at
> the last moment). :)
Yeah there was an RFC and it was voted no:
On 19.09.2018 at 18:53, BohwaZ wrote:
> On Mon, 17 Sep 2018 15:16:13 +0200 / "Christoph M. Becker"
> said :
>
>> ext/sqlite3 requires libsqlite ≥ 3.3.9[1] which has been released on
>> 2007-01-04[2] (i.e. more than eleven years ago!). ext/pdo_sqlite has
>> no specific version requirement;
On Mon, 17 Sep 2018 15:16:13 +0200 / "Christoph M. Becker"
said :
> Hi!
>
> We bundle an unmodified libsqlite3 for at least two years. Since then
> all updates go into any dev, alpha and beta releases, while security
> patches (usually backports from libsqlite3) go into stable branches.
>
>
Hi,
> -Original Message-
> From: Nikita Popov
> Sent: Monday, September 17, 2018 7:07 PM
> To: Christoph Becker
> Cc: PHP internals
> Subject: Re: [PHP-DEV] Unbundle libsqlite3?
>
> On Mon, Sep 17, 2018 at 3:16 PM Christoph M. Becker
> wrote:
&
Le 17/09/2018 à 15:16, Christoph M. Becker a écrit :
> Hi!
>
> We bundle an unmodified libsqlite3 for at least two years. Since then
> all updates go into any dev, alpha and beta releases, while security
> patches (usually backports from libsqlite3) go into stable branches.
>
> ext/sqlite3
On Mon, Sep 17, 2018 at 3:16 PM Christoph M. Becker
wrote:
> Hi!
>
> We bundle an unmodified libsqlite3 for at least two years. Since then
> all updates go into any dev, alpha and beta releases, while security
> patches (usually backports from libsqlite3) go into stable branches.
>
>
On 17.09.2018 at 16:44, Johannes Schlüter wrote:
> On Mo, 2018-09-17 at 15:16 +0200, Christoph M. Becker wrote:
>
>> So is there any particular reason why we still bundle libsqlite3?
>
> An issue is that users often don't control the version being used and
> SQLite adds features to it's SQL
On Mo, 2018-09-17 at 15:16 +0200, Christoph M. Becker wrote:
> So is there any particular reason why we still bundle libsqlite3?
An issue is that users often don't control the version being used and
SQLite adds features to it's SQL dialect from time to time. At the
moment, with the bundled
Hi
Den man. 17. sep. 2018 kl. 15.16 skrev Christoph M. Becker :
>
> Hi!
>
> We bundle an unmodified libsqlite3 for at least two years. Since then
> all updates go into any dev, alpha and beta releases, while security
> patches (usually backports from libsqlite3) go into stable branches.
>
>
Hi!
We bundle an unmodified libsqlite3 for at least two years. Since then
all updates go into any dev, alpha and beta releases, while security
patches (usually backports from libsqlite3) go into stable branches.
ext/sqlite3 requires libsqlite ≥ 3.3.9[1] which has been released on
2007-01-04[2]
11 matches
Mail list logo
