Last Updated: 11/21/2001

11/21/2001 - Release 0.80 is officially released! This is the first official release of ArunaDB.

11/2001 - Completed the documentation for existing classes. Created the ArunaDB.com web site. It's looking good. Published the ArunaDB project on the Ruby RAA list. Fixed remaining bugs in the A_BTree class.

10/2001 - The A_BTree rewrite is complete and the A_BTree class is running twice as fast now. Performance is good. Still running intense A_BTree tests and fixing obscure btree errors.

9/2001 - Created my first large table by importing data from a large Oracle database that I had sitting around from an earlier project. It's running too slow. I created the A_Buffer class to improve performance. This caused a near full re-write of the btree class. Bummer! I Love Ruby even more than before.

8/2001 - Added triggers, indexes, sequences, and views. These classes and the A_Table class are looking good.

7/2001 - Added transaction support to the A_Table class. This included begin_transaction, commit, and rollback.

6/2001 - Created several intense btree test scripts that unveiled some obscure btree errors. Fixed most of these obscure errors. Created apack and aunpack as an alternative means to store data in the btree (Marshal.Dump was used). These were much faster than using Arrays with Marshal.dump in Ruby 1.6.4. In Ruby 1.6.5, Arrays are much faster and this performance difference was not so great. I looked at using Array.pack and String.unpack but they did not adequately support all the data types I wanted to store in the btree, so I created apack and aunpack.

4/2001 - While refining the btree class, I created the A_FileStore class so that many btrees could reside and a single file and a single btree could span many physical files. This inspired a rewrite of the btree class. It also expaned the features of the btree a lot. Also created the A_Catalog class to store information about btrees and filestore. It was too easy to change the parameters of the call to A_BTree.new() and A_FileStore.new() and these changes did not work very well with the existing objects sitting in the files. Now the information store in the catalog overrules the information provided in the new() commands when the object name already exists.

3/2001 - Implemented basic btree and table classes, these work great. I love Ruby! Decided to call this project ArunaDB. Aruna is Sanskrit for Ruby. Aruna.com is already taken so I decided to use ArunaDB.com.

2/2001 - Decided that a database server would be my first Ruby Project. Began proto-tying a database server in Ruby. I really like the Ruby language.

1/2001 - I received and read "Programming Ruby" by David Thomas and Andrew Hunt. It's an excellent book.  After reading this book, it appears that a database server would be fairly easy to implement in Ruby. I am looking for my first Ruby project because I feel that having a project will make learning Ruby easier.

12/2000 - While looking for my next project, I discovered Ruby. I decided that I would use Ruby as a means to update my Object Oriented programming skills. This decision was made based on several emails I stumbled across about how much fun Ruby is. I purchased "Programming Ruby" by David Thomas and Andrew Hunt.