problem with tests and custom mysql fulltext indexes
Reported by stanislav | May 1st, 2008 @ 10:49 AM
I'm using Rails 2.0.2 / MySQL 5.0.45
I think it's a kind of bug/problem for tests and mysql fulltext indexes, which doesn't have a common workaround.
So, it goes like this:
I have this in my migration:
execute "CREATE FULLTEXT INDEX fulltext_summary ON indexed_stories (summary)"
where "summary" is mysql text field.
The problem that I see is that when running "rake db:test:prepare" it always loads "schema.rb". However in it, instead of the above custom execute we have this line:
add_index "indexed_stories", ["summary"], :name => "fulltext_summary"
which tries to create a normal index and dies with:
Mysql::Error: BLOB/TEXT column 'summary' used in key specification without a key length: CREATE INDEX `fulltext_title_summary` ON `indexed_stories` (`title`, `summary`)
Is there a work-around for such situations where we're using custom sql in migrations?
Comments and changes to this ticket
-
Jeff Dean May 1st, 2008 @ 10:59 AM
In environment.rb uncomment:
config.active_record.schema_format = :sql
Then when you run db:test:prepare --trace you'll notice that it uses clone_structure instead of clone.
-
stanislav May 1st, 2008 @ 02:56 PM
Thank you for the support. It's OK now. You can close this ticket. It was a kind of obvious resolution, but....
Best Wishes
-
Joshua Peek June 3rd, 2008 @ 08:05 PM
- → State changed from “new” to “invalid”
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".
