On 2024-06-18 05:25, Matteo Beccati wrote:
Hi,
Sure, you need to have the same version of libpq that PHP was built
with. But nothing prevents your script using pdo_pgsql or ext/pgsql to
connect to another version of postgres running either on the same
machine or a different one.
Right; t
Hi all!
I've been reading the internals mailing list for some time and giving my 2
cents here and there.
Now I have created a new wiki account (erickcomp) and I'd like to request
RFC karma for a new RFC I worked on during my recent studies of the php-src.
Thank you,
Erick Lima
Hi, I m all for the changes this update should not preclude any 10.0 client
to connect to a 9.x server. cheers.
Hi,
Il 17/06/2024 19:21, Peter Kokot ha scritto:
When building for a certain PostgreSQL version, the pq library gets
linked to the extension and then this PostgreSQL version needs to be
used, yes. If you build for 10.0, then you need to use that exact
version. Linux packages have this resolved b
On Mon, 17 Jun 2024 at 19:16, Matteo Beccati wrote:
>
> Hi,
>
> Il 17/06/2024 19:03, Peter Kokot ha scritto:
> > On Mon, 17 Jun 2024 at 18:58, Pierre wrote:
> >>
> >> Would id affect the possibility to use an old PostgreSQL (eg. 9.6) via
> >> PHP (PDO or ext-pgsql) ?
> >>
> >> If so, it might be
Hi,
Il 17/06/2024 19:03, Peter Kokot ha scritto:
On Mon, 17 Jun 2024 at 18:58, Pierre wrote:
Would id affect the possibility to use an old PostgreSQL (eg. 9.6) via
PHP (PDO or ext-pgsql) ?
If so, it might be a dangerous move for oldest projects, you sometime
can upgrade PHP and your software
Hi
On 6/13/24 21:48, Timo Tijhof wrote:
I ask because MediaWiki's main "text" database table is an
immutable/append-only store where we store the text of each page revision
since ~2004. It is stored as serialised blobs of a value class. There have
been a number of different implementations over
On Mon, 17 Jun 2024 at 18:58, Pierre wrote:
>
> Would id affect the possibility to use an old PostgreSQL (eg. 9.6) via
> PHP (PDO or ext-pgsql) ?
>
> If so, it might be a dangerous move for oldest projects, you sometime
> can upgrade PHP and your software easily, but can't upgrade the database
> s
Le 14/06/2024 à 22:54, Peter Kokot a écrit :
Hello,
we're thinking of bumping the minimum PostgreSQL version supported by PHP from
current version 9.1 to version 10.0:
https://github.com/php/php-src/pull/14540
A list of PostgreSQL versions and their EOL dates can be seen at
https://en.wikipedia
On Fri, Jun 14, 2024, at 8:54 PM, Peter Kokot wrote:
> Hello,
>
> we're thinking of bumping the minimum PostgreSQL version supported by PHP from
> current version 9.1 to version 10.0:
> https://github.com/php/php-src/pull/14540
>
> A list of PostgreSQL versions and their EOL dates can be seen at
>
Hi,
Il 03/06/2024 09:27, Matteo Beccati ha scritto:
Hi internals,
I've just opened the vote for the "PDO driver specific parsers" RFC. The
RFC contains a single vote which requires a 2/3 majority to pass. Voting
runs 2 weeks until 2024-06-17 15:00 UTC.
Please find the following resources fo
Hi,
Il 14/06/2024 22:54, Peter Kokot ha scritto:
Hello,
we're thinking of bumping the minimum PostgreSQL version supported by PHP from
current version 9.1 to version 10.0:
https://github.com/php/php-src/pull/14540
Anyone have any concerns or thoughts about this?
I'm very happy with it.
Che
> On Jun 17, 2024, at 8:54 AM, Bilge wrote:
> Furthermore, for absolute clarity and the avoidance of doubt, I believe this
> guiding principle can be enshrined on the following single sentence:
>
> "We cannot remove features from a static class that would otherwise be
> present in a standar
On 17/06/2024 13:49, Bilge wrote:
On 16/06/2024 14:32, Mike Schinkel wrote:
Not supporting all features used in the wild would result in
developers not being able to use static classes for new and/or
refactored code if they believe they need those excluded
features. This would s
On 16/06/2024 14:32, Mike Schinkel wrote:
Not supporting all features used in the wild would result in
developers not being able to use static classes for new and/or
refactored code if they believe they need those excluded features.
This would stop developers from signaling their
On Fri, 14 Jun 2024, Lanre wrote:
> Coming from the property hooks/ asymmetric visibility dude, that's pretty
> rich.
Please, ad-hominem (and other) attacks are not welcome on this list.
Please familiarise yourself with the mailinglist rules
(https://github.com/php/php-src/blob/master/docs/mai
16 matches
Mail list logo
