Following the popularity and attendance at last year’s code sprint a repeat of the event was held on the two days prior to the UK IUA. The objective of the event was to introduce, and in some cases re-introduce, the sprinters to the Ingres source code and build environment; either a pre-configured VMWare virtual machine provided on a flash drive or the same image running as a machine in Amazon EC2 if required.
Projects compiled from the community and from other sources were considered and ranked according to the expertise in the room.
In no particular order they are:
- Improved SOUNDEX() function Daitch Mokotoff
- Default to enable command history in terminal monitor on Linux and UNIX
- Drupal with Ingres running in Amazon EC2
- Pull ABF parser into the terminal monitor
- CASE statements in ABF
- IF statements within the terminal monitor
- Rename Column
- Bit column
- optimizedb from within SQL
- createdb from within SQL (Paul and Alex)
- Online sysmod
- DBfunctions as well as db procedures. Difference between procedures only return a status
- Storing a QEP so that you can reference it later
- Renamedb
- ckpdb – include the ability to use bzip2/gzip for compressed checkpoints
- Incremental checkpoint
- copydb with no logging
- Utility to map process ids to gcc port numbers
- List databases that you don’t want to use no logging
- SQL Terminal monitor \s[hell] syntax to be extended to: \s[hell] [/full/path/to/file|{shell command;...}]
Projects were assigned and investigated and were quickly excluded if proved more challenging and time consuming than the available two days. Look out for the design documents for some of the implementation coming soon, take a look at the tickets from Jun 7 and 8 at http://bugs.ingres.com/timeline.
I worked with Roy Simon from Boarding Data A/S, taking a copy Drupal 6.1 which included updates for using Ingres built from the iuasprint09 SVN branch as its repository. We also built the Ingres PHP driver with the latest patch.
All of the pre-requisites were installed and configurations updated so that when the machine is started, Ingres is started as a service and Drupal’s installation wizard is available by directing a Web browser to the Drupal Web page. Once we had it running correctly, I used the Amazon Web Services (AWS) plug-in in Eclipse and created an Amazon Machine Image (AMI).
Although more an exercise in packaging than coding it was still satisfying to launch a machine in the Amazon Cloud and just start using it.
These early sprints are a way to have a guided tour of the Ingres source code with people who work with it every day. I look forward to seeing you at the next one, which may be before the next IUA 08/Jun/2010.
