Rasmus Lerdorf wrote:
What is true is that most people no longer build PHP at all. They just
end up with whatever their provider has installed or with whatever
packages they end up installing when they install the PHP app they want
to use. Both Wordpress and Drupal depends on php-mysql on Ubuntu,
Rewriting perfectly functional mysql code to use mysqli is not a trivial
move, just as are the problems of re-writing PHP5.2 code to work cleanly
on 5.4. ISP's are stuck between keeping customers - who are most likely
not even very computer literate - working while fighting the problems that
c
Christopher Jones wrote:
Adam, can you:
1. Add this link to the RFC?:
https://wikis.oracle.com/display/mysql/Converting+to+MySQLi
Now that IS a good start!
Adding that to core documentation as well could be helpful?
But in a lot of cases it is the pre-loaded 'abstraction layer' that may be t
Hi
On 13 November 2012 00:29, Rasmus Lerdorf wrote:
> That is simply not true. If you download PHP and do ./configure && make
> install you do not get MySQL support. You have to explicitly specify
> that you want it.
My apologies then. I actually checked a ./configure output, and saw
under Confi
Leigh wrote:
Hi
On 13 November 2012 00:29, Rasmus Lerdorf wrote:
That is simply not true. If you download PHP and do ./configure && make
install you do not get MySQL support. You have to explicitly specify
that you want it.
My apologies then. I actually checked a ./configure output, and saw
Rasmus Lerdorf in php.internals (Mon, 12 Nov 2012 16:29:35 -0800):
>What is true is that most people no longer build PHP at all. They just
>end up with whatever their provider has installed or with whatever
>packages they end up installing when they install the PHP app they want
>to use. Both Wordp
Lester Caine wrote:
Their ISP has had to switch E_DEPRECATED off for all of their users simply to
keep legacy sites running.
And this made me laugh ... just trying to log into a new ISP system ...
ERROR: PleskFatalException
Unable to connect to database: mysql_connect()
How many ISP's use ple
Jan Ehrhardt wrote:
> Many people are now gradually moving from Drupal 6 to Drupal 7. For
> Drupal 7 PHP 5.3 is recommended:
> http://drupal.org/requirements
(Somewhat off-topic)
Conversely, WordPress is not moving to 5.3+ for a while, we still have a
huge userbase on 5.2 (~66%): http://wordpress
hi Rasmus,
On Tue, Nov 13, 2012 at 1:29 AM, Rasmus Lerdorf wrote:
> On 11/12/2012 07:24 AM, Leigh wrote:
>> Hi,
>>
>>> We put ext/mysql in a (security) bug fix maintenance mode only
>>> years ago. Too many ignore those attempts to get rid of ext/mysql.
>>
>> Maybe it's time to put it into full no
Hi Rasmus:
> Both Wordpress and Drupal depends on php-mysql on Ubuntu, for
> example.
>
> It would be good if we could get the majority of the major PHP apps to
> commit to supporting mysqli along the same timeframe as marking this
> deprecated.
WordPress is moving in that direction:
http://core
Reinis Rozitis wrote:
>> Rewriting perfectly functional mysql code to use mysqli is not a
>trivial
>> move, just as are the problems of re-writing PHP5.2 code to work
>cleanly
>> on 5.4. ISP's are stuck between keeping customers - who are most
>likely
>> not even very computer literate - wo
There's one important thing that I think you all are missing here. You keep
bringing up that we should just use the normal "deprecation" process. The
problem is that the deprecation process was never designed for a feature
like this.
Look at what was deprecated and removed so far. We deprecated re
On 13 November 2012 23:49, Johannes Schlüter wrote:
>
>
> Reinis Rozitis wrote:
>
>>> Rewriting perfectly functional mysql code to use mysqli is not a
>>trivial
>>> move, just as are the problems of re-writing PHP5.2 code to work
>>cleanly
>>> on 5.4. ISP's are stuck between keeping customers -
On 14 November 2012 00:07, Anthony Ferrara wrote:
> There's one important thing that I think you all are missing here. You keep
> bringing up that we should just use the normal "deprecation" process. The
> problem is that the deprecation process was never designed for a feature
> like this.
Serio
Am 13.11.2012 17:07, schrieb Anthony Ferrara:
> What I would suggest, is not adding E_DEPRECATED for 5.5. Instead,
> officially deprecate it in the docs. Then start a PR campaign to get
> projects like WP to switch away from it. Get the word out there as much as
> possible. Then in 1 to 2 years whe
2012/11/13 Anthony Ferrara
> There's one important thing that I think you all are missing here. You keep
> bringing up that we should just use the normal "deprecation" process. The
> problem is that the deprecation process was never designed for a feature
> like this.
>
> Look at what was depreca
Hi Internals,
with the first alpha going to be tagged today and officially released
on Thursday, I went ahead and created the 5.5 branch. Merging should
be still straight forward, but it's going to be 5.3 -> 5.4 -> 5.5 ->
master.
I know this is a mess, but I think we'll have to live with that fo
On Tue, Nov 13, 2012 at 8:28 AM, Arvids Godjuks
wrote:
> It took me like 10 minutes of "Search & Replace" in my IDE to make a switch
> to mysqli and a few more hours to validate that everything is ok and catch
> places where search & replace failed. The amount of work is overestimated,
> especiall
On 13 November 2012 16:07, Anthony Ferrara wrote:
> What I would suggest, is not adding E_DEPRECATED for 5.5. Instead,
> officially deprecate it in the docs. Then start a PR campaign to get
> projects like WP to switch away from it. Get the word out there as much as
> possible. Then in 1 to 2 year
hi,
On Tue, Nov 13, 2012 at 7:29 PM, Ronald Chmara wrote:
> On Tue, Nov 13, 2012 at 8:28 AM, Arvids Godjuks
> wrote:
>> It took me like 10 minutes of "Search & Replace" in my IDE to make a switch
>> to mysqli and a few more hours to validate that everything is ok and catch
>> places where search
On Nov 13, 2012, at 18:44, David Soria Parra wrote:
> Following the versioning scheme of 5.4.x version, I versioned master as
> 5.5.99 until we decide if it's going to be a 5.6.0 or a 6.0.0
Repeating what was said for 5.4.99: I don't think this is good. This makes
version comparison harder. U
On Nov 13, 2012, at 18:07, Anthony Ferrara wrote:
> There's one important thing that I think you all are missing here. You keep
> bringing up that we should just use the normal "deprecation" process. The
> problem is that the deprecation process was never designed for a feature like
> this.
On Nov 13, 2012, at 18:28, Arvids Godjuks wrote:
> It took me like 10 minutes of "Search & Replace" in my IDE to make a switch
> to mysqli and a few more hours to validate that everything is ok and catch
> places where search & replace failed. The amount of work is overestimated,
> especially
On Tue, 13 Nov 2012, Johannes Schlüter wrote:
>
>
> On Nov 13, 2012, at 18:44, David Soria Parra wrote:
>
> > Following the versioning scheme of 5.4.x version, I versioned master as
> > 5.5.99 until we decide if it's going to be a 5.6.0 or a 6.0.0
>
> Repeating what was said for 5.4.99: I don
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Makes sense, I'll bumped the version to 5.6.0-dev
On Tue 13 Nov 2012 08:23:31 PM CET, Derick Rethans wrote:
> On Tue, 13 Nov 2012, Johannes Schlüter wrote:
>
>>
>>
>> On Nov 13, 2012, at 18:44, David Soria Parra wrote:
>>
>>> Following the versioning
On Tue, Nov 13, 2012 at 11:17 AM, Adam Harvey wrote:
> On 14 November 2012 00:07, Anthony Ferrara wrote:
>> There's one important thing that I think you all are missing here. You keep
>> bringing up that we should just use the normal "deprecation" process. The
>> problem is that the deprecation p
On 11/13/2012 01:40 AM, Lester Caine wrote:
Christopher Jones wrote:
When users of 5.5 stumble on the new messages, we can then simply
point them to the RFC.
I think this is part of the problem. The material from the RFC's
should be used as a source to update the core documentation? Rather
t
Hi Anthony:
On Tue, Nov 13, 2012 at 11:07:53AM -0500, Anthony Ferrara wrote:
>
> Wordpress's latest trunk uses ext/mysql.
WordPress uses a "wpdb" object. Switching out the class to a mysqli
based one is pretty simple and a patch exists. I have a feeling it'll
make it into 3.6.
--Dan
--
T H
I see several problems with deprecating ext/mysql:
- The extension is not broken. The problem is the bad usage.
It can be used safely, and good developers have been doing
so for ages, by creating php wrappers.
In magic quotes, the work has been the opposite. The developers
had been detecting the f
Am 14.11.2012 00:23, schrieb Ángel González:
So the problem really moves onto the CMS providers, do they support
new php versions and drop customers in shared hosting, do they delay
supporting the new php versions, or do they reimplement mysql_*
in php?
We are talking about ~1.5 years until ext/m
Hi!
> But with a strong warning that on a later version of PHP things WILL stop
> working altogether? More often now E_DEPRECATED is already switched off
> simply
Why again we must breaking people's working code?
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(40
Hi!
>> 2. Mention how to turn off E_DEPRECATED warnings in the RFC?
>
> Done and done. I've added a (short) workarounds section towards the
> bottom, which can be moved up later if the RFC is accepted.
Please note currently PHP has no mechanism of turning off any warnings
or errors. The best y
32 matches
Mail list logo
