[5/30/2006]

I sepnt some of my time today researching the feature differences between the Apache Derby and the MySQL databases. I created a Feature Matrix posted in the "Notes" section of the MysqlDerbyMigration page. The purpose of this Feature Matrix is to provide information about the features that the Target System can offer. This will be helpful in deciding if the target system have the necessary features needed for the Source System or not.

The Feature Matrix is grouped into two categories for now: Data Integrity and Database Object. The Data Integrity group shows Support of ACID transactions, savepoints, Foreign Key, locking or Multiversion Concurrency Control (MVCC). The Database Object group shows Advanced database objects like views, schemas, temporary tables.

A detailed version of this feature matrix as well as links to additional resources I used for creating this matrix can be found at:

I also looked into the dump utility provided by the MySQL database: "mysqldump". This dump utility is a backup program that can be used to dump a database or a collection of databases for backup or for transferring the data. The dump contains SQL statements to create the table or populate it, or both. An example of a dump output is shown below:

Now, I need to analyze the above dump and make necessary changes to the above statements so that they can be executed on Apache Derby. Once the translation is done, the database can be migrated.

[5/31/2006]

I started off today with writing a piece of code that parses the data from the mysql dump. I then started working on finding the comparison between MySQL and Derby's datatypes such numeric types, string types, and Data and Time types. The document is posted in the "Notes" section of the MysqlDerbyMigration page.