Matt has a good post on the recent push to make people use PHP 5. He makes several good points, and I’m just jumping on the same bandwagon.. forcing a version # change, just because the engine works better is pointless. Going into the political arena a little bit, making people switch to PHP 5 is like changing CAFE standards, it won’t do a thing for the billions of cars already out there, and it won’t change the basic dependence on crude oil. It’s just a lot of hot air to make the choir sing to themselves, again.

I’ve been running PHP 5 on my systems for the past 3 years, without any issues. Even some of the code I wrote in PHP 4, works flawlessly (with the same bugs) in PHP 5 as PHP4. Which brings me to the main point.. End Users don’t care or want to know what the engine is doing . If the application does something they want, they’ll use it. If …

Yes, even though MySQL 5.1 is in beta (soon to be RC), our surveys show that folks are using 5.1 already for production use.

If you’re using 5.1 for production apps, I’d appreciate it if you could drop me a line and let me know what motivated you to move up to 5.1. What 5.1 features made you take the plunge? As we’re in the midst of planning features for the upcoming server versions, knowing what you like about 5.1 and what improvements you’d like to see over what we did in 5.1 would be a great help. Shoot me a note at rschumacher@mysql.com.

Thanks!

OSCON, the Open Source Convention organized by O'Reilly is coming up next week (July 23rd-27th, Portland, OR).

MySQL AB will be present in the exhibition area and we will also be giving some talks:

• Brian Aker: Extending MySQL, Swiss Army Knife Approach
• Kaj Arnö: The MySQL Architecture of Participation
• Mårten Mickos: The Path to IPO …

I’m not quite sure how to feel about this but I feel today has been more productive than all of last week. hrrm..

(Filling 1 through 41 is an exercise left to the reader… I just like the number 42)

handler::info can be called on a handler that has never had ::exeternal_lock called. So if you rely on a call to handler::external_lock to set up something (e.g. a pointer to a transaction object), you may explode in a heap.

See: Bug#26793

A

Version 1.4.3 of the innotop MySQL and InnoDB monitor is out. This release fixes some minor bugs and feature annoyances, and at last innotop has thorough documentation, available online!

MySQL K.K., the Japanese arm of the open source database developer MySQL AB, has announced three new initiatives aimed at strengthening its expansion in the Japanese market: New Tokyo offices; a Japanese-language beta version of the MySQL 5.1 User's Manual; and the addition of a new corporate partner.

First, we download ACC from www.aspectc.net and make it following the README. ACC script tacc can automatically compile aspect files (with suffix .acc) with regular .c files. To use tacc, we need setup several environment variables:
For example, in .bashrc

export PATH=$PATH:.:/ACC_PATH/bin
export CC=tacc
export SRCROOT=/PBXT_SOURCE_CODE_PATH/src
export AR=accar

SRCROOT is our source code (i.e. pbxt) directory. We also put .acc files in the same source code directory. Then, we can run ./configure inside PBXT source code directory as before. E.g,

./configure --with-mysql=/home/build/mysql-51 --libdir=/home/build/test/lib/mysql --with-debug=full

It will automatically generate a makefile which uses ACC command.
Note, in our case, we have mixed .cc and .c files. Since ACC does not work with .cc, we need use gcc to link file instead of using g++. So, we have …

• Perl, MySQL, Scalability consulting - Develooper