Ok, it seems that MySQL AB is finally committing to fix up PDO_MySQL and to generally accept the fact that PDO is the future. Of course mysqli will also be actively maintained. But they will also make mysqlnd play nicely with PDO etc.

There's budgets and time lines for the project so things are already moving along and developers to the project will soon be assigned. Lukas also mentions updated on PHP's side - validating that the documentation for the extensions (mysql and mysqli) are up to date and correct.

he bad news: mysqlnd might have bugs. How to report and debug these bugs - using mysqli_debug() - is subject of this posting.

They step you through the process for finding out what's causing the problems (internal versus external debugging) and how to make client traces with the mysqi extension to make it even easier for the developers to track down the problem. They also suggest a few things to send along with your bug report - like the PHP code calling it or the SQL you're using to select/update/insert/delete the data from your database.

There still seems to be a lot of confusion over the differences between the two extensions despite the length of time that mysqli has been in the wild. I wanted to briefly review the four major benefits of mysqli.

Here's the list

• Prepared Statements
• Secure MySQL connections
• Multi query
• Object Oriented Interface

He also includes a few more links to further information (besides the explanation for each of the topics listed above) including an article from the Zend Developer Zone and a tutorial covering making the switch to MySQLi.

I've decided that a little investigation in weather it can connect,query and close faster than the MYSQL function I prefer the MYSQLi version as the _connect function is a lot more organised with the DB select in it.

The code used for the benchmarks is simple - just a connect, query and close (no fetch). The results of running each 1500 times shows that, by a pretty narrow margin, the MySQL extension comes in around 92 milliseconds faster than MySQLi.

This article will illustrate some basic techniques for using the mysqli interface. This is a great tool to use in php5 because it doesn't need any include libraries like PEAR, etc; it is compiled right into the distribution.

They start things simple, showing how to make the mysqli connection in your script, including how to set up the connection parameters. They move quickly into making queries on the database - first a simple one with a loop and then a more complex example with a prepared query. They wrap things up by helping you create a simple class that works as a bit of an abstraction layer to query and report on the results returned.

I'd like to point out that one of the greatest services to the PHP community that Zend is providing is the free Zend Core for Oracle and Zend Core for DB2. The latest versions install PHP 5.1.6. The little known secret is that these 2 installers are perfect for MySQL as the mysql and mysqli extensions are included in the release.

He also recommends it for the IISers out there because of the FastCGI support built in.

The reason behind using persistent connections is of course reducing number of connects which are rather expensive, even though they are much faster with MySQL than with most other databases.

They go on to talk about:

• issues with the number of active connections that could come up
• the use of too many connections at once
• why persistent connections are disabled in the new mysqli extension

I must say that the "mysqli" extension offers an impressive set of features, which can be implemented right from the very beginning. However, and speaking of its cool features, in the next few lines, I'm going to show you a few more. Over the course of this last tutorial, I'll be covering some other methods and properties, mainly aimed at finding the IDs after inserting new rows, and obtaining information about specific table fields.

They touch on the fetch_array, data_seek, fetch_assoc, fetch_field, and fetch_seek functions, giving examples and other assicated properties along the way.

This is the second part of the series "Using mysqli with PHP 5." Welcome back. In three tutorials, this series shows how to use the most important methods and properties included in the "mysqli" extension that comes with PHP 5, in order to take advantage of the new features bundled with MySQL 4.1 and above.

In part one they introduced the extension, providing the background for those just joining in. In this latest part, they take it to the next level and talk about these new handy functions - one to save the updates/additions you're making to the database and the other to undo those changes quickly and easily. As always, there's plenty of examples, explainations, and code to go around.

All right, I know that you're now saying that's not breaking news, since the implementation of objects is an old programming feature. However, PHP 5 has a lot more to offer when it comes to using MySQL. If you're using MySQL 4.1 and above, the good news is that PHP 5 offers a fairly comprehensive extension, called "mysqli," which allows you to interact natively with MySQL via an object-based approach, aside from taking advantage of the new functionality provided by the database server.

They start with a basic introduction of the extension, including how to perform some of the basic bits of functionality on your MySQL database - connecting, getting host information, and even performing a simple query. They then get into the "real power" behind the mysqli extension, the ability to run multiple queries and handle natively the results of those queries easily. They wrap it all up with a look at using prepared statements with this extension, showing the prepare, bind_param, and execute functions.