Afrasyab Bashir wrote:
> Just to add, sadly enough the solution I wrote was true only for MySQL
> version 5.0.6+ :(   'cos on MySQL 6.0 it's still a problem.
> 
> On Jul 2, 10:42�am, Matthew Rudy Jacobs <[EMAIL PROTECTED]

By now, MySQL 6.0.7 and Rails 2.1.2 still have the problem.

Mysql::Error: #42000Specified key was too long; max key length is 767 
bytes: CREATE UNIQUE INDEX `unique_schema_migrations` ON 
`schema_migrations` (`version`)

Which one should fix the problem? MySQL or Rails team?
This problem blocks Rails' test.
:(
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to