Re: Landing page for MySQL materials

From: Date: Mon, 31 Oct 2011 19:22:17 +0000
Subject: Re: Landing page for MySQL materials
References: 1  Groups: php.doc 
Request: Send a blank email to phpdoc+get-969383318@lists.php.net to get a copy of this message
On Mon, Oct 31, 2011 at 14:29, Ulf Wendel <ulf.wendel@oracle.com> wrote: > 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) > [...] > > XML >  SDO >  SDO-DAS-Relational >  SDO_DAS_XML > I really hated the SDO/SCA situation when it came around few years ago, but never managed to do anything about it. Since our core sections are <set>s these days we can stack up additional steps if we want like you are suggesting. I like option#1, groupping all the mysql* exts into <book>s together into its own <set>, keeping the xml:id BC, with the exception of intro.mysql serving as a "welcome to the MySQL infopage". -Hannes

« previous php.doc (#969383318) next »