On 14 Jul 2008, at 01:34, Hannes Magnusson wrote:
On Mon, Jul 14, 2008 at 01:28, Daniel Convissor
<[EMAIL PROTECTED]> wrote:
On Sun, Jul 13, 2008 at 01:46:29PM +0200, Hannes Magnusson wrote:
On Sat, Jul 12, 2008 at 15:04, Daniel Convissor
<[EMAIL PROTECTED]> wrote:
Hi Folks:
The various http://php.net/mysqli_* function names redirects go
to the
old mysql_* functions rather than the "new" myslqi_* functions.
Is this
intentional?
No.
Okay. So I did some more poking around to figure out how the
redirecting
is done. I recalled hearing that an SQLite database was involved.
I see
that the work is done by phpweb/include/manual-lookup.inc and that an
SQLite is used when available and various string replacements / file
system checks otherwise.
http://us.php.net/mysqli_close
mistakenly shows mysql_close
http://us3.php.net/mysqli_close
properly shows mysqli_close
I see you put a fix for the non-SQLite lookups in revision 1.33 of
manual-lookup.inc.
I went to examine the SQLite database, manual-lookup.sqlite, which is
supposed to be in phpweb/backend. But I didn't see it on cvs.php.net
http://cvs.php.net/viewvc.cgi/phpweb/backend/. I'm confused.
Its not in CVS, it is generated by the rsync box using
systems/gen-phpweb-sqlite-db.php
There are some open related phpweb bug reports too... please have a
look while resolving this issue.
Also note that this sqlite database is rsynced to mirrors so you may
download it from a mirror too. Also note that only about half of the
mirrors use this sqlite database.
Regards,
Philip
