This project is archived and is in readonly mode.
Add unique index test fails on sqlite2
Reported by Frederick Cheung | April 21st, 2008 @ 09:18 AM
The test_add_index in migration_test.rb fails on sqlite2 when attempting to add a unique index on a column. The value of that column is null for all rows, which sqlite2 considers violates the uniqueness constrain (other databases don't seem to care). Seeding some data into that column fixes the problem.
Comments and changes to this ticket
-
Michael Koziarski April 21st, 2008 @ 09:36 AM
This causes failures on mysql. I believe because key is a reserved word?
-
Repository April 23rd, 2008 @ 03:25 AM
(from [ae51013c3f7b8a8579fcb99d889ed80e9dd75797]) Provide data for the key column otherwise adding a unique index will fail. [#30 state:closed]
-
Michael Koziarski April 23rd, 2008 @ 03:25 AM
- State changed from new to resolved
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Attachments
Tags
Referenced by
- 2188 Encoding error in Ruby1.9 for templates ActionView::TemplateError (incompatible character encodin...