Ok, if you're reading this.. you'll notice the new look. Things that have changed.

1. 
   
2. New Server : Single processor, less powerful than before.. but this has less traffic.
   
3. RHEL 4 : Redhat Enterprise Linux 4
   
4. PHP 5.1 : Custom built version of PHP 5.1
   
5. MySQL 5 : Upgraded to MySQL 5
   
6. S9y : Changed backend from Wordpress to Serendipity.
   

Why did I do this ? Because I can, and because my other server is being used for mail. It's also close to a new year, so I wanted to turn a new leaf, try something new, and have some fun. Resolutions for next year (in no particular order)

• 
  
• Learn more JavaScript so I can do more "AJAX"y stuff.
  …

Well, I'm into day three of my vacation and so far the destruction of the new house is proceeding nicely:

I get the feeling by the time January 3 rolls around I'll be happy to just sit and work on the MySQL docs, a nice vacation from my vacation.

Greetings!  I joined MySQL this week as Senior Product Manager over MySQL Network.  I am honored to be working with the people who have built the #1 open source database in the world!  This is truly a “kid in a candy store” opportunity for me and my promise to the loyal MySQL ”fandom” is that I will work with our current and prospective customers to build the suite of Network services into the defacto standard for proactively managing and supporting the MySQL database engine. 

If you are a current Network customer, thank you for your business.  Please consider me a resource at your disposal for helping you to be more efficient and strategic as you leverage MySQL going forward.  Your input and feedback is key to our success and is greatly appreciated by yours truly!  I encourage you to post early and often your comments and suggestions …

These instructions are for the common SIMPLE situation of deploying a WebObjects application on ONE server where the server also acts as the web server. The database can be on the same server too or any other server requiring only that the EOModel connection URL point to the database wherever it is. This is especially useful for first time WO deployment newbies. But first, if you have not already configured the server for WebObjects deployment, then read that entry in this blog first and configure your server.
[UPDATE 4/25/2006: Building on Tiger 10.4.6, WO 5.3.1 for deploy on Panther 10.3.9, WO 5.2.3]

The sample chapter of Essential PHP Security for MySQL's Developer Zone is now available:

• Chapter 2, Forms and URLs

This chapter discusses form processing and the most common types of attacks that you need to be aware of when dealing with data from forms and URLs. You will learn about attacks such as cross-site scripting (XSS) and cross-site request forgeries (CSRF), as well as how to spoof forms and raw HTTP requests manually. By the end of the chapter, you will not only see examples of these attacks, but also what practices you can employ to help …

First let me say I'm not a prude, but neither do I have a mouth like a toilet. But I do find the acronym RTFM incredibly offensive, it may be that some people using it don't actually know what it means and it can be said the F stands for something other than the obvious but either way I don't like it. I've nothing wrong with acronyms but what I don't like about it is the idea that you're swearing at somebody you don't even know, who in their ignorance for one reason or other didn't read a manual. Would you for example say to somebody who asks you the time "Buy a ******* watch". The other problem is often people don't actually tell you which manual it is your supposed to go and ******* read.

Anyway the point of this little rant was to tell you to go and read a manual. Well not just any manual but the MySQL Reference manual. From time to time I'll have a browse to see what's in there and from time to time I pickup some great tips. For …

Somebody recently asked a question about warnings in the MySQL Stored Procedure forum, the question its self was pretty easy but it raised another issue.

The question was "How can I see warnings when MySQL reports them". The easy answer is to simply type "SHOW WARNINGS;" on the MySQL command line, however the show warnings command only shows the last error message, thats fine if you actually type "SHOW WARNINGS;" immediately after the statement that had the problem but if you make a mistake or wait for something else to go wrong then the warning message is removed and replaced by something else.

The answer of course is not to make a mistake, but for people like me who come from a different background, in my case Oracle, the commands are different. I'm forever typing "SHO WARNINGS;" or "SHOW ERROR;" both of which result in another error and hence I lose the original message.

But here's a tip I used when …

I’ve been accepted to present at the MySQL Users Conference 2006 held in Santa Clara, California next year. My paper will be particularly targeting Oracle Developers, and will be combined with another presentation targeting Oracle DBA’s.

I’ll also be developing demonstrations with the upcoming MySQL Sakila Test Database by Mike Hillyer from MySQL AB.