Scientific Technology Systems

Awesome. Truly awesome. I'm really at a loss for words to describe the
experience.

The plane is a Czechoslovakian-built Aero L-39 aircraft, a low-wing,
tandem seating, all metal turbofan powered aircraft designed for basic
and advanced training, including weapon delivery practicing, as well as
for light attack tasks. More information about the plane is here:
http://www.l39.com

Photos are here:
http://www.scitechsys.com/photos/viewer.php?albid=8&stage=1

We departed from Sacramento Executive and headed out over Lake Tahoe.
90 Bank turns, aileron rolls, stalls, barrel rolls and a zoom demo. I
was in heaven! It was over way too soon. On the way back, we shot a
practice approach to Mather Airfield (used to be Mather Air Force
Base). I did most of the flying - except for the few minutes I took
videos and pictures with my digital camera.

156 gallons of Jet A at $5.40 / gal = $842.40 and worth every penny!
Now I have to figure out how I'm going to stay current for the next few
months as I recover my flying budget.

1.0 hours of jet time in my logbook! Not bad for a 100 hour pilot.

These are the videos:
Taxing out:

Taking off from SAC.

Flying over Emerald Bay, Lake Tahoe

Low approach at MHR

Landing back at SAC

Taxing in

I've been spending some time working on a port of Drupal 4.7 to use an Ingres2006 database. It's been interesting, but it has highlighted several shortcomings of Ingres and the php driver for Ingres (from PECL).

The most glaring absence is that of automatically incrementing columns. Yes, I'm aware of sequences, but one can't assign an expression as the default. It's also not possible to use rules (triggers) and procedures to update the column with a value from the sequence. One can create an after insert rule, but if the column is part of the Primary Key (and cannot be NULL) this approach isn't possible. The Drupal uses an id value as the primary key for many tables.

Now Drupal, in the code, says that it doesn't use the auto incrementing feature for compatibility reasons. During the port, I immediately ran across a function (inserts into the watchdog table) that uses auto incrementing feature. When I reported this on the Drupal bug tracking site - the response was that it was as designed for performance reasons. So much for compatibility.

BLOBs and CLOBs have also been an issue. In Ingres, one can only assign a string literal of 2000 characters to in SQL. So, for the port, I've increased the page size of the cache table to 64k and use varchar(32000) for the data. I've also used the gzcompress function in PHP to make the cache data small enough to fit in the column.

The Ingres PHP Driver from PECL is also a little quirky. Not only do the functions not follow the same parameter order as, say, MySQL, but at least one (ingres_error) was responsible for a segmentation fault in Apache.

The port, for right now, is broken. I'm still resolving issues. There's actually something to see now - Drupal on Ingres