| From | Sent On | Attachments |
|---|---|---|
| Philip Olson | Jul 10, 2011 10:03 am | |
| Reindl Harald | Jul 10, 2011 10:15 am | |
| Mike Robinson | Jul 10, 2011 1:20 pm | |
| Pierre Joye | Jul 10, 2011 2:01 pm | |
| Matthew Weier O'Phinney | Jul 11, 2011 7:27 am | |
| Adam Harvey | Jul 11, 2011 7:40 am | |
| Keloran | Jul 11, 2011 8:10 am | |
| Christopher Jones | Jul 11, 2011 8:41 am | |
| Paul Dragoonis | Jul 11, 2011 9:30 am | |
| Matthew Weier O'Phinney | Jul 11, 2011 10:56 am | |
| Mike Robinson | Jul 11, 2011 11:47 am | |
| Larry Garfield | Jul 14, 2011 6:38 pm | |
| Johannes Schlüter | Jul 15, 2011 5:46 am | |
| Reindl Harald | Jul 15, 2011 5:55 am | |
| Ulf Wendel | Jul 15, 2011 6:04 am | |
| Johannes Schlüter | Jul 15, 2011 6:09 am | |
| Philip Olson | Jul 15, 2011 10:15 pm | |
| Julien Pauli | Jul 18, 2011 1:01 am |
| Subject: | [PHP-DEV] deprecating ext/mysql | |
|---|---|---|
| From: | Philip Olson (phi...@roshambo.org) | |
| Date: | Jul 10, 2011 10:03:13 am | |
| List: | net.php.lists.internals | |
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 officially
convince people to stop using this old extension. This means:
- Add notes that refer to it as deprecated - Recommend and link alternatives - Include examples of alternatives
There are two alternative extensions: pdo_mysql and mysqli, with PDO being the
PHP way and main focus of future endeavors. Right? Please don't digress into the
PDO v2 fiasco here.
What this means to ext/mysql:
- Softly deprecate ext/mysql with education (docs) starting today - Not adding E_DEPRECATED errors in 5.4, but revisit for 5.5/6.0 - Add pdo_mysql examples within the ext/mysql docs that mimic the current examples, but occasionally introduce features like prepared statements - Focus energy on cleaning up the pdo_mysql and mysqli documentation - Create a general "The MySQL situation" document that explains the situation
The PHP community has been recommending alternatives for several years now, 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





