MySQL AB is building on its European organisation. With a new sales office in the Netherlands, MySQL will focus on supporting corporate customers and users throughout the Benelux region.

I was poking around in the MySQL source code, namely in sql/sql_yacc.yy, and found a hidden treat: there’s a SHOW COLUMN TYPES command. It’s fun to read source code! The command is undocumented, but does work. It returns just two rows, which give information about TINYINT and TINYINT UNSIGNED. And it has been in the source for a long time, certainly since version 4.1.21. There’s even a status counter for it in the SHOW STATUS command: Com_show_column_types.

I set out Monday morning to Perros-Guirec, a village at the west coast of France, west from St-Malo. We have an important meeting with MySQL customer and I had to be there. Everything was carefully planned, I had my tickets and I knew when to leave.. on time..

Well, it didn't go the way I expected..


So I set out at 05:30 to the train station of Aschaffenburg to Darmstadt. Train was at 06:06 and would arrive like 06:52 just in time to take the train to Paris at 07:02. I managed to stay awake, but when lots of people got on train I got distracted and a bit dreaming away. I heard the speaker say 'Darmstadt' and I get out. But …

Amid recent discussions about calling MySQL stored procedures from PHP or similar API-type interfaces, and mentions of difficulties in doing so, I thought I would post some notes about my experiences. When I first tried to use stored procedures from PHP, I discovered that it worked some of the time, but I did not take the time to delve into the whys or the wherefores. It was also mentioned by some that the mysqli interface was necessary in order to properly interact with stored procedures, but I have since determined that that is in fact not the case. I now conclude that the mysql interface works with stored procedures just fine, and that is fine with me since I am perfectly at home with this interface.

The only issue appears to be when returning a resultset. It's not at all intuitive, but in order to return a resultset from a stored procedure to PHP, one must have either the multiple-statements connect option or the multiple-results …

Step by step Apache Friends becomes more international: After the translation of our website into (traditional) Chinese Apache Friends now also reaches the South American continent: Kudos to André Domarques, who spend over the last weeks much of his spare time for the translation of all our website contents into Brazilian Portuguese.

To the Brazilian Portuguese translation

OK, so I returned from vacation late last night, after putting almost 1700 miles on my car this past four days. A friend of mine had his Master's thesis show (in furniture design) down in Savannah, Georgia. It was a fantastic time, and Ezra's work is truly astonishing, but I was quite exhausted after the long drives to and from Columbus, Ohio.

You may remember that I have been helping my twin brother learn PHP and MySQL programming. I'm pleased to say that he is progressing quite well! Every time we Skype chat, he seems to have picked up more and more programming vocabulary and is understanding some of the trickier concepts fairly well. My teaching is ongoing. I have advised him to try and learn five new PHP functions every time he sits down to code, and to practice the functions by using them in his work. For instance, …

Yesterday evening I finally released the procedure converter at Sourceforge.net. I am quite satisfied with the result, it covers quite a lot. But the user interface is virtuallt non-existant, and the parsing needs some improvement. The problem is that for more complex conversion tasks (like shifting order for function parameters) I would need better parsing of the source code.

Features:

1. converts CREATE PROCEDURE/FUNCTION syntax
2. adds semi-colon at the end of statements
3. converts IF and WHILE statements to MySQL syntax
4. sorts the code in the correct order, with declarations at the top and instructions
5. after that
6. removes @, [ and ] from identifiers
7. converts comments to MySQL syntax (a space in the 3rd position for -- comments)
8. adds a CONTINUE HANDLER FOR NOT FOUND if the procedure contains cursors
9. comments out GOTO and …

After coming back from holidays on the 6th of September, I've been able to work on the project with a refreshed mind again!

I expected to have finished coding by now, but after putting all the components together, I ran into an occasional 'segmentation fault'. I've been looking for the problem, but only with the help from one of my colleagues I was able to address the causes.

For the first cause, I should explain a little bit about how ORTE handles issues:
As I explained before, ORTE works with 'publishers' and 'subscribers'. ORTE periodically invokes a callback function on the publisher side, which is meant to prepare the data for sending in a memory buffer. When the callback function finishes, ORTE reads the buffer and copies it to a memory buffer on the subscriber side. It then invokes the subscriber callback function which is meant to process the incoming data.

So what went wrong in my …

Unfortunately, after having my blog on the net for about 4 months, spam bots have found my blog. To prevent any further bot comments to appear on my blog, I've switched on 'word verification' for comments.

Please don't let it hold you back from posting comments on my blog. All your (non-spam) input is very much appreciated!

Blog: http://sqlbusrt.blogspot.com/

Project website: http://sqlbusrt.sourceforge.net/

Just the notes for the installation steps on a clean OS X Tiger Server 10.4.7 setup.