I get an error during migration that says:
ActiveRecord::ActiveRecordError: Specified key was too long; max key length is 767 bytes

Environment – Mac os x – Leopard
Mysql 5.0.5 (and also on Mysql6.0)

Here is the log:

/Applications/Mingle.app/Contents/Resources/app/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:128:in `log’: ActiveRecord::ActiveRecordError: Specified key was too long; max key length is 767 bytes: CREATE UNIQUE INDEX `index_events_on_origin_type_and_origin_id` ON events (`origin_type`, `origin_id`) (ActiveRecord::StatementInvalid) from /Applications/Mingle.app/Contents/Resources/app/vendor/gems/activerecord-jdbc-adapter-0.7.1/lib/active_record/connection_adapters/jdbc_adapter.rb:502:in `execute’ from /Applications/Mingle.app/Contents/Resources/app/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/schema_statements.rb:197:in `add_index’ from /Applications/Mingle.app/Contents/Resources/app/vendor/rails/activerecord/lib/active_record/migration.rb:275:in `method_missing’ from /Applications/Mingle.app/Contents/Resources/app/vendor/rails/activerecord/lib/active_record/migration.rb:259:in `say_with_time’ from file:/Applications/Mingle.app/Contents/Resources/app/vendor/java/jruby-complete.jar!/benchmark.rb:293:in `measure’ from /Applications/Mingle.app/Contents/Resources/app/vendor/rails/activerecord/lib/active_record/migration.rb:259:in `say_with_time’ from /Applications/Mingle.app/Contents/Resources/app/vendor/rails/activerecord/lib/active_record/migration.rb:273:in `method_missing’ from /Applications/Mingle.app/Contents/Resources/app/db/migrate/045_add_events_table.rb:11:in `up’ ... 7 levels… from /Applications/Mingle.app/Contents/Resources/app/vendor/rails/activerecord/lib/active_record/migration.rb:288:in `migrate’ from /Applications/Mingle.app/Contents/Resources/app/app/models/license.rb:83:in `do_migration’ from

Any pointers?

Thanks,
Suresh

Hi Suresh -

This looks to be an issue with MySQL configuration. The data in those columns is certainly not large enough to cause this error. We have not seen this in the field. We will research this immediately and get back with an answer shortly.

-David

Hi Suresh,

Can you please create a support request for this issue and attach your MySQL configuration file? A support request can be created at http://studios.thoughtworks.com/mingle-project-intelligence/support-requests. This is most likely a MySQL configuration issue, but we have not been able to determine how to change the configuration to cause this error. Your configuration file might help us out a lot.

Thanks for helping us track this down.

Jay

Has there been any resolution to this issue yet?

Hi Jason,

Our support people determined that the problem was that the Mingle database was a MySQL 6.0 database. Mingle will only run on MySQL 5.0 or PostgreSQL 8.1 or 8.2.

Jay

http://studios.thoughtworks.com/mingle/2.0/help/system_requirements.html