Hello everyone,
The MySQL team is considering ways to cleanup and clarify the MySQL
documentation. Two main reasons:
a) ext/mysql will be deprecated in the (distant) future
b) there are already 7 MySQL extensions
- mysql, mysqli, pdo_mysql
- mysqlnd
- mysqlnd_qc, mysqlnd_ms, mysqlnd_uh
.. a word on a) to prevent misinformation: using the old mysql extension
for new developments is not recommended,
http://news.php.net/php.internals/53799 . The docs will be updated
accordingly to give migration hints. Users are requested to either make
use of mysqli or pdo_mysql.
One idea is to turn the current php.net/mysql into a MySQL landing page.
So, either:
(1a) Use xml:id=intro.mysql as the landing page
(1b) Move mysqli.overview to mysql.overview
(1c) Probably a few other things, and as such, hijack reference/mysql/
-- or --
(2) Keep the info separate from reference/mysql (but have
php.net/mysql redirect elsewhere)
I can't think of a perfect place for this landing page, which is one
reason why hijacking reference/mysql feels like an option. It does not
belong in our overloaded appendix. One concern: it may confuse users who
expect reference/mysql/ to only contain ext/mysql info. Maybe.
What do people think? I prefer (1) but would understand (2) or perhaps a
new option as (3).
Regards,
Ulf
PS: MySQL is certainly the most extreme example but there are other
cases too where a landing page could come handy for readers.
DB
Abstrations
PDO
link to PDO_MySQL
Vendor Specific
SQLite
SQLite
SQLite3
MySQL
mysqli
mysqlnd
mysqlnd_ms
mysqlnd_qc
mysqlnd_uh
mysql
Other
Memcache
Memcache
Memcached
XML
SDO
SDO-DAS-Relational
SDO_DAS_XML
