My work life is really fragmented at present, so I’ve decided a split approach in answer to Dave Rosenberg’s How I Work–what I have learned so far .

CentOS 4.3
FireFox 1.5, ThunderBird 1.5, Gaim, SSH, Skype, Open Office 2.
Maybe not all of these every day, but some combination of each day –> MySQL 4.1, MySQL 5.0, MySQL 5.1, MySQL Workbench, Eclipse 3.1, J2DK 1.4.2, J2DK 5.0, Apache Tomcat 5.0.28, Apache Httpd 2.0.53, JMeter.

Presently also configuring a new laptop drive running …

I’ve been using VNCViewer from RealVNC under Linux to remote connect to an older machine running windows. Two reasons, I don’t need yet another screen on my desk, and I need windows to adequately test and use the MySQL GUI products, in particular MySQL Workbench.

I never realised there was a better way, particularly over a local network, a command called rdesktop which is capable of natively speaking Remote Desktop Protocol (RDP).

$ su -
$ yum install rdesktop

This did only give me version 1.3.1. The current version 1.4.1 available from the rdesktop Website does provide greater commands including the syntax I use.

su -
cd /src
wget http://optusnet.dl.sourceforge.net/sourceforge/rdesktop/rdesktop-1.4.1.tar.gz
tar xvfz rdesktop-1.4.1.tar.gz
cd rdesktop-1.4.1
./configure
make
make install …

Thursday afternoon I stopped by the Usenix Annual Technical Conference on my way out of Boston to be on a panel led by Stephen Walli on Open Source Business models. I got to share the panel with Miguel de Icaza from Novell, and Mike Olsen from SleepyCat/Oracle. It was a great panel, I even got to make use of my "open source can be built on top of a tip jar economy" quote :)

There was an excellent piece of insight I gained from Mike Olson. When asked about receiving value from the community, I had said that what I find most of value was "well qualified bug reports", but what Mike thought was of more value was users who provided validation of the product's value. I've been involved in many open source projects, some well known, and some completely unknown outside of a small group. I've never concerned myself about validation since I have been lucky to have have it come naturally where I have wanted it. What Mike was pointing out was …

I was talking with someone the other day about my Lineo experiences, and it recalled to my mind just how insane the dot-com boom was. Lineo was on a strong path to IPO - we had almost no revenues (a few million dollars), were grossly unprofitable, had no differentiating product (embedded Linux, which customers were happy to buy consulting around, but not pay for the software itself, and wouldn't pay anything for support), and had a massive burn rate.

This was IPO material?

To be fair to us, a large reason that we had the burn rate was because our investment bankers (very respectable, big-name bankers, mind you) told us that we needed a large employee base to justify a high valuation. Think about that for a minute. Not revenues. Not profits. Employees. And so we acquired 6 companies, went from 40 to 440 people virtually overnight, and completed our S-1. …

There was this bug that I wrote about earlier which caused certain Stored Procedures to crash when they were executed more often than once.

I noticed in the bug report and in the change log that this bug will be fixed in MySQL 5.0.23.

I just saw a Microsoft commercial video clip using the slogan

"Better and more simple Visual Basic - goodbye anger, hello fun"

What do they want to tell us? Does that mean, the former version of Visual Studio/Visual Basic caused anger? Do they worsen their old product to make advertising for the new one?

My next thought would be - how will they advertise when the next version comes out? Will they again say, that the now current release causes anger or something similar?

I don't think that's good advertising.

DELIMITER //

CREATE SCHEMA fractal //
USE fractal //

CREATE TABLE disp (
id INT PRIMARY KEY,
content VARCHAR(1000)
) //

CREATE TABLE shade (
id INT PRIMARY KEY,
value INT
) //

INSERT INTO shade (id,value) VALUES (0,ORD(' ')),(1,ORD('.')),(2,ORD(',')),
(3,ORD('-')),(4,ORD('~')),(5,ORD('*')),(6,ORD(':')),(7,ORD(';')),(8,ORD('+')),
(9,ORD('o')),(10,ORD('O')),(11,ORD('&')),(12,ORD('%')),(13,ORD('@')) //

CREATE PROCEDURE mandelbrot (IN x_max INT, IN y_max INT)
BEGIN
DECLARE x INT DEFAULT 0;
DECLARE y INT DEFAULT 0;
DECLARE xf0 FLOAT;
DECLARE yf0 FLOAT;
DECLARE xf1 FLOAT;
DECLARE yf1 FLOAT;
DECLARE tf FLOAT;
DECLARE l INT;
DECLARE l_max INT;
DECLARE buffer VARCHAR(1000);
DECLARE tint INT;
TRUNCATE disp;
SELECT MAX(id) INTO l_max FROM shade LIMIT 1;
WHILE y<y_max DO
SET buffer='';
SET x=0;
WHILE x<x_max DO
SET xf0=x*4.0/x_max-2.0;
SET yf0=y*4.0/y_max-2.0;
SET xf1=xf0;
SET yf1=yf0;
SET l=0;
WHILE l<l_max AND xf1*xf1+yf1*yf1<4.0 DO
  SET tf=xf1*xf1-yf1*yf1+xf0;
  SET …

This document is a user report on the MaxDB Synchronization Manager. The article describes the use of the MaxDB Synchronization Manager during United Drugs Annual Convention from a technical standpoint. It gives an example of the magnitude of possible application of the MaxDB Synchronization Manager. Written for developers, the user report contains warnings on common pitfalls and gives hints how to circumvent the problems.

My friends Theo Schlossnagle, Laura Thomson and Chris Shiflett are each presenting at ApacheCon Europe. They are each excellent presenters with solid content - I have seen Theo present at a previous ApacheCon, caught Laura at several OSCONs and finally saw Shiflett speak at the PHP Quebec conference earlier this year.

The deal is simple - sign up for any of their tutorials before the early bird deadline for the conference closes (on June 6th) and get complementary copies of some of the speaker’s book(s).

The sessions are:

• Advanced Production Troubleshooting …

MySQL does not always make a right decision about indexes usage.
Condsider a simple table:

PLAIN TEXT SQL:

1. CREATE TABLE `t2` (
2. `ID` int(11) DEFAULT NULL,
3. `ID1` int(11) DEFAULT NULL,
4. `SUBNAME` varchar(32) DEFAULT NULL,
5. KEY `ID1` (`ID1`)
6. ) ENGINE=MyISAM DEFAULT CHARSET=latin1

SELECT COUNT(*) FROM t2;
250001 (V1)

SELECT COUNT(*) FROM t2 WHERE ID1=1;
83036 (V2)
(execution time = 110 ms)

That is index selectivity by condition (ID1=1) is V2/V1 = 0.3321 or 33.21%

It is said (e.g. book "SQL Tuning") if selectivity over 20% then a full table scan is preferable than an index access.
As far as I know Oracle alway chooses a full table scan if selectivity over 25%.

…