• Full: Download WordPress 2.9.1 mysqli database class
• Patch: Download WordPress 2.9.1 mysqli database class

• Full: Download WordPress 2.9 mysqli database class
• Patch: Download WordPress 2.9 mysqli database class

Patch contents

Index: wp-includes/wp-db.php
===================================================================
--- wp-includes/wp-db.php	(revision 19)
+++ wp-includes/wp-db.php	(working copy)
@@ -367,9 +367,12 @@
 			$this->collate = DB_COLLATE;

 		$this->dbuser = $dbuser;
+
+		// $this->dbh = @mysql_connect($dbhost, $dbuser, $dbpassword, true);
+		$this->dbh = new mysqli($dbhost, $dbuser, $dbpassword, $dbname); 

-		$this->dbh = @mysql_connect($dbhost, $dbuser, $dbpassword, true);
-		if (!$this->dbh) {
+		// if (!$this->dbh) {
+		if ($this->dbh->connect_error || mysqli_connect_error()) { // remember $mysqli->connect_error is broken in PHP < 5.2.9
 			$this->bail(sprintf(/*WP_I18N_DB_CONN_ERROR*/"
 <h1>Error establishing a database connection</h1>
 <p>This either means that the username and password information in your <code>wp-config.php</code> file is incorrect or we can't contact the database server at <code>%s</code>. This could mean your host's database server is down.</p>
@@ -386,18 +389,21 @@
 		$this->ready = true;

 		if ( !empty($this->charset) ) {
+			$this->dbh->set_charset($this->charset);
+			$this->real_escape = true;
+			/*
 			if ( function_exists('mysql_set_charset') ) {
 				mysql_set_charset($this->charset, $this->dbh);
-				$this->real_escape = true;
 			} else {
 				$collation_query = "SET NAMES '{$this->charset}'";
 				if ( !empty($this->collate) )
 					$collation_query .= " COLLATE '{$this->collate}'";
 				$this->query($collation_query);
-			}
+			}*/
 		}

-		$this->select($dbname);
+		// selection of database with mysql happens when connecting
+		// $this->select($dbname);
 	}

 	/**
@@ -454,6 +460,9 @@
 	 * @return null Always null.
 	 */
 	function select($db) {
+
+		return true; // database selection happens in constructor when usng mysqli
+
 		if (!@mysql_select_db($db, $this->dbh)) {
 			$this->ready = false;
 			$this->bail(sprintf(/*WP_I18N_DB_SELECT_DB*/'
@@ -475,7 +484,7 @@

 	function _real_escape($string) {
 		if ( $this->dbh && $this->real_escape )
-			return mysql_real_escape_string( $string, $this->dbh );
+			return $this->dbh->real_escape_string( $string );
 		else
 			return addslashes( $string );
 	}
@@ -579,7 +588,7 @@
 	function print_error($str = '') {
 		global $EZSQL_ERROR;

-		if (!$str) $str = mysql_error($this->dbh);
+		if (!$str) $str = $this->dbh->error;
 		$EZSQL_ERROR[] = array ('query' => $this->last_query, 'error_str' => $str);

 		if ( $this->suppress_errors )
@@ -703,39 +712,40 @@
 		if ( defined('SAVEQUERIES') && SAVEQUERIES )
 			$this->timer_start();

-		$this->result = @mysql_query($query, $this->dbh);
+		$this->result = $this->dbh->query($query);
 		++$this->num_queries;

 		if ( defined('SAVEQUERIES') && SAVEQUERIES )
 			$this->queries[] = array( $query, $this->timer_stop(), $this->get_caller() );

 		// If there is an error then take note of it..
-		if ( $this->last_error = mysql_error($this->dbh) ) {
+		if ( $this->last_error = $this->dbh->error) {
 			$this->print_error();
 			return false;
 		}

 		if ( preg_match("/^\\s*(insert|delete|update|replace|alter) /i",$query) ) {
-			$this->rows_affected = mysql_affected_rows($this->dbh);
+			$this->rows_affected = $this->db->affected_rows;
 			// Take note of the insert_id
 			if ( preg_match("/^\\s*(insert|replace) /i",$query) ) {
-				$this->insert_id = mysql_insert_id($this->dbh);
+				$this->insert_id = $this->db->insert_id;
 			}
 			// Return number of rows affected
 			$return_val = $this->rows_affected;
 		} else {
 			$i = 0;
-			while ($i < @mysql_num_fields($this->result)) {
-				$this->col_info[$i] = @mysql_fetch_field($this->result);
+			while ($i < $this->result->field_count) {
+				$this->col_info[$i] = @$this->result->fetch_field();
 				$i++;
 			}
 			$num_rows = 0;
-			while ( $row = @mysql_fetch_object($this->result) ) {
+			while ( $row = @$this->result->fetch_object() ) {
 				$this->last_result[$num_rows] = $row;
 				$num_rows++;
 			}

-			@mysql_free_result($this->result);
+			// no more need for freeing results, they ARE free! 
+			// @mysql_free_result($this->result);

 			// Log number of rows the query returned
 			$this->num_rows = $num_rows;
@@ -1138,4 +1148,5 @@
 	 */
 	$wpdb = new wpdb(DB_USER, DB_PASSWORD, DB_NAME, DB_HOST);
 }
+
 ?>

When I am trying to optimize my PHP code, one of my prefered tools is xdebug. It provides me with excellent error messages, outputs code tracing files & insight into memory usage.

By using kcachegrind or webgrind – wincachegrind crashes *all* the time – to parse the cachegrind files created by xdebug, you get a good idea of what your code is doing most of the time. It’ll show you which functions are called, by who, which arguments are passed and tons more. Check it out.

Now, there was one small thing I couldn’t find anywhere. A program to parse the trace files that xdebug generates. True, xdebug already provides the option to output this information into HTML, but it’s not really what I was looking for. I want to get quick information in the blink of an eye! That’s why I have created my own trace file parser, based on PHP of course.

What is it?

This xdebug trace parser will show you, for each function:

• How much memory was used on entry & exit
• How much time it costed to execute the function
• The exact line the function was called from plus insight into the code by clicking a link
• Whether the function is native PHP or not

It also has a basic “alerting” feature, which will allow you to set triggers on memory usage & execution time. You can specifiy that if the memory or time jump is greater than a certain value, to show this in the output.

Requirements

It should be obvious that you’ll need to install and configure xdebug for your PHP installation. See http://www.xdebug.org for more information on this.

Your xdebug config should look a bit like this, don’t forget to update your paths

[XDebug]
;; Only Zend OR (!) XDebug
zend_extension_ts="\php\ext\php_xdebug-2.0.4-5.2.8.dll"
xdebug.auto_trace=1
xdebug.trace_format=1
xdebug.profiler_append=1
xdebug.profiler_enable=1
xdebug.profiler_enable_trigger=0
xdebug.collect_params=4
xdebug.collect_return=1
xdebug.trace_output_dir="D:\webserver\xdebug"
xdebug.trace_output_name= %t.trace
xdebug.profiler_output_name = %s.%t.profile
xdebug.profiler_output_dir="D:\webserver\xdebug"

Download

Now, give it a try and downlod the xdebug trace file parser here!

Usage

Once you’ve downloaded the trace file parser, extract it to a directory inside your website root and surf to the URL. If everything works out you should be able to select trace files onceyou have ran an other PHP script on your server. This trace file parser will *not* show it’s own traces because that would make things even more complicated!

Comments & suggestions!

1. GETNCVPS: Save 10% on all VPS packages
2. HOSTING4U: Save 10% on shared hosting plans
3. GETMECHEAPER: Save 88 cents on most domain TLD extensions

Tip #1 Caching expansion

There are several good caching modules out there. Some are unstable or neglected by the Drupal community, others are just not worth the hassle installing. Personally I prefer using Advanced Cache module. The advanced caching module is mostly a set of patches and a supporting module to bring caching to Drupal core in places where it is needed yet currently unavailable. These include caching nodes, comments, taxonomy (terms, trees, vocabularies and terms-per-node), path aliases, and search results.

This module will give you your first performance boost, even if you’re using standard Drupal cache to support it. There are also two (minor?) downsides when using this module. First one being that you have to hack Drupal core and second one is that it hasn’t received a lot of feedback for Drupal 6.

Also download the patches I have contributed to ensure *everything* is being cached correctly and that the patches work on the latest Drupal release.

• http://drupal.org/project/advcache
• http://drupal.org/files/issues/node_102.patch patch #1
• http://drupal.org/files/issues/taxonomy_56.patch patch #2
• Patches for advanced cache – topic

Tip #2 Memcache

Memcache is probably the easiest performance improvement you can get. No patching required, you just need to set up a memcached daemon and you’ll be on your way.

You will want to split your caches up into several bins. This will reduce the impact of a cache rebuild on your server. You can find all the information on how to set up and install this module on it’s project page.

• http://drupal.org/project/memcache
• Download memcache on nix/windows

Tip #3 Proxy caching

Using a proxy to cache your static files is a good idea. And caching dynamic pages too is an even better idea! But… aiii… again, this involves hacking Drupal core.
You can choose between varnish, squid or apache’s mod_cache. They all work the same and none of them has proven me to be a “better option”.

Tip #4 Alternative search solution

The Drupal search will cause a very nasty load on your database server if you get a few requests at the same time. But don’t panick, there are several options available to lighten the load.

Currently, apache SOLR is considered the Drupal way to go if you’re looking into an alternative search solution. Admitted, this module does get more support and has more options than any other. On the other hand, it will put strain on your web an database server while doing indexing & re-indexing. The maintainers of the Apache SOLR module are looking into ways to improve this.

Anyway, untill they have fixed the module, I’d suggest using the Sphinxsearch module. It has fewer options, but Sphinx is able to index your website without using the Drupal API or PHP.

• http://drupal.org/project/sphinx
• Sphinx search

Tip #5 Minimize the use of the views module

The views module must be one of the greatest things since sliced bread. It allows you to easily set up new aggregations of nodes, users, …
Too bad we can’t say the same about it’s performance. When you use this module, you have to know that you’re on thin ice. A wrong decision in your admin cp can easily cause a slow query to be generated and that’ll affect your whole site.
My advice here is to hard code as many views as possible. It’ll take a bit longer, but it’ll save you pain in the long run.

http://www.rdlt.com/postcodes-van-alle-gemeentes-van-belgie-met-gps-coordinaten

Moesten er toch nog fouten zijn ingeslopen, laat me dit dan weten in een reactie!

Alvast veel plezier ermee! Moest je deze database ergens gebruiken, laat het me dan even weten!

For a project of mine, I had to find a database that contained all cities of Belgium with their postal codes and GPS locations (longitude & latitude). Since I couldn’t find such a database (or I had to pay too f***ing much) I decided to create one myself.

Since I’m such a commie, I’ve decided to share this database with anyone that needs it! Please refer to this page to download the database. At this time it’s only available in Dutch. Maybe some day I’ll take the time to translate it into english. Maybe some cash would make me work faster? Send your donations to PayPal address: thomas@rdlt.com …

Download database of all cities in Belgium with postal code and GPS location!

Download een database met alle steden in België met postcode en GPS locatie!