Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:53808 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 77872 invoked from network); 10 Jul 2011 21:01:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Jul 2011 21:01:30 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.160.170 mail-gy0-f170.google.com Received: from [209.85.160.170] ([209.85.160.170:51255] helo=mail-gy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 98/D1-63663-9231A1E4 for ; Sun, 10 Jul 2011 17:01:29 -0400 Received: by gyb13 with SMTP id 13so1472005gyb.29 for ; Sun, 10 Jul 2011 14:01:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=bFGEUmAMW1QZBlrTi+fmJZ7IoFL93acz1iNVgC6nU7g=; b=s//AMR9zrfywpX4vszI4IzXvgJkgaWE3p0J4TVICvIaPj5p3Q9ACpFNC9tzDxCYoHN v329klecJTrZHsobqHfTdTO9gTAYGlp/FfKB3oqbGXSnAcscswauZVuVaE5s0dQskpXE 5FBvM+NmI6xymw983lAXFk2c2hCWw9OaOoGIY= MIME-Version: 1.0 Received: by 10.146.105.16 with SMTP id d16mr3016922yac.13.1310331686338; Sun, 10 Jul 2011 14:01:26 -0700 (PDT) Received: by 10.147.137.11 with HTTP; Sun, 10 Jul 2011 14:01:26 -0700 (PDT) In-Reply-To: <9F1FA580-FD3F-4C3F-9E26-51A095CF6EE9@roshambo.org> References: <9F1FA580-FD3F-4C3F-9E26-51A095CF6EE9@roshambo.org> Date: Sun, 10 Jul 2011 23:01:26 +0200 Message-ID: To: Philip Olson Cc: PHP Developers Mailing List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] deprecating ext/mysql From: pierre.php@gmail.com (Pierre Joye) hi, As I would love to kill ext/mysql, it is up to the mysql developers to deci= de. Cheers, On Sun, Jul 10, 2011 at 7:03 PM, Philip Olson wrote: > Greetings PHP geeks, > > Don't panic! This is not a proposal to add errors or remove this popular = extension. Not yet anyway, because it's too popular to do that now. > > The documentation team is discussing the database security situation, and= educating users to move away from the commonly used ext/mysql extension is= part of this. > > This proposal only deals with education, and requests permission to offic= ially convince people to stop using this old extension. This means: > > =A0- Add notes that refer to it as deprecated > =A0- Recommend and link alternatives > =A0- Include examples of alternatives > > There are two alternative extensions: pdo_mysql and mysqli, with PDO bein= g the PHP way and main focus of future endeavors. Right? Please don't digre= ss into the PDO v2 fiasco here. > > What this means to ext/mysql: > > =A0- Softly deprecate ext/mysql with education (docs) starting today > =A0- Not adding E_DEPRECATED errors in 5.4, but revisit for 5.5/6.0 > =A0- Add pdo_mysql examples within the ext/mysql docs that mimic the curr= ent > =A0 examples, but occasionally introduce features like prepared statement= s > =A0- Focus energy on cleaning up the pdo_mysql and mysqli documentation > =A0- Create a general "The MySQL situation" document that explains the si= tuation > > The PHP community has been recommending alternatives for several years no= w, so hopefully this won't be a new concept or shock to most users. > > Regards, > Philip > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --=20 Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org