Proposals for MySQL Conference

Some of the bloggers on Planet MySQL are sharing their proposals for the upcoming 2008 MySQL Conference & Expo. Hereby, I follow their example and give you mine. The first proposal I submitted is on PHPUnit and will showcase Michael Lively Jr.'s port of DbUnit:

Testing PHP/MySQL Applications with PHPUnit/DbUnit In the last decade, PHP has developed from a niche language for adding dynamic functionality to small websites to a powerful tool making strong inroads into large-scale Web systems. Critical business logic like this needs to work correctly. But how do you ensure that it does? You test it, of course. To make code testing viable, good tool support is needed. This is where PHPUnit comes into play. It is a member of the xUnit family of testing frameworks and provides both a framework that makes the writing of tests easy as well as the functionality to easily run the tests and analyse their results. This session introduces the audience to PHPUnit's DbUnit extension that makes the writing of tests that interact with databases more convenient and easier.
The scond proposal takes a piece of code for data partitioning that I wrote a long time ago for phpOpenTracker and relates it to MySQL 5.1's native support for this concept:
(Custom) Data Partitioning - Then & Now Partitioning allows you to distribute portions of individual tables across a filesystem according to rules which you can set largely as needed. In effect, different portions of a table are stored as separate tables in different locations. Some queries can be greatly optimized in virtue of the fact that data satisfying a given WHERE clause can be stored only on one or more partitions, thereby excluding any remaining partitions from the search. Starting with version 5.1, MySQL natively supports partitioning. But partioning can even be implemented with older versions using MyISAM Merge Tables and custom application logic. This session will first present a small PHP library that rewrites SQL queries to a merge table to use as few individual tables as possible before it will give an overview of MySQL 5.1's native partioning implementation.
If you are interested in these topics, share your opinion in the comments. Thanks!