Tuesday, March 13, 2007

Drop Derby and goes back to MySql

After my rant yesterday about Derby not supporting column rename, I checked ActiveRecord-JDBC document for Derby and column_rename is not one of the supported feature.

Here is the list of databases and the level of support taken from the document.
  • MySQL - Complete support
  • PostgreSQL - Complete support
  • Oracle - Complete support
  • Microsoft SQL Server - Complete support except for change_column_default
  • DB2 - Complete, except for the migrations:
    • change_column
    • change_column_default
    • remove_column
    • rename_column
    • add_index
    • remove_index
    • rename_table
  • FireBird - Complete, except for change_column_default and rename_column
  • Derby - Complete, except for:
    • change_column
    • change_column_default
    • remove_column
    • rename_column
  • HSQLDB - Complete
Since MySql is completely supported, I switch to using MySql as the database back end for development.

I did notice one little problem with Netbeans today. The "Generate" menu item disappeared from the menu for some reason. I closed and reopened Netbeans but that didn't do anything. Finally, I closed the project, reopen it and the Generate menu item came back. It only happened once. I don't remember what I did to cause the problem though.

1 comment:

Leon said...

Just wanted to clarify your statements on migrations for DB2. If you are using IBM-provided DB2 Ruby driver and DB2 Rails adapter (get them with Starter Toolkit for DB2 on Rails at http://www.alphaworks.ibm.com/tech/db2onrails) then only
- rename_column(table_name, column_name, new_column_name) and
- change_column(table_name, column_name, type, options)are not implemented (yet). See our blog at http://db2onrails.com/pages/migrations for additional information on migrations and DB2.