Hobo Hobo → Hobo 1.1

Comments and changes to this ticket

• 

  Bryan Larsen May 19th, 2010 @ 06:15 PM

  • State changed from “new” to “wontfix”

  Unfortunately, this ia a bug in Rails itself, which generates insanely long index names. This is actually a much more significant problem with Oracle, which has a much shorter limit.

  To work around this issue, you'll need to supply an explicit name:

   index [:some_long_id, :another_long_id], :unique => true, :name => "some_index_name"
  

• 

  Matt Jones May 20th, 2010 @ 02:11 AM

  • Milestone set to “Hobo 1.1”
  • Tag changed from “migration-generator” to “enhancement, migration-generator”
  • State changed from “wontfix” to “open”
  • Title changed from “Hobo migration generator generating too long index names for PostgreSQL” to “Make index generation pay attention to DB limits”
  • Assigned user set to “Matt Jones”

  Actually, we can now fix this! Yay! Rails just accepted this patch so we actually have a shot at knowing how long an index name can be before bad things happen.

  Or at the very least, the new add_index code whines but doesn't die when the name is too long.

  We'll need to figure out the best UI for this - should the migration generator ask, or just warn? There's also the mess from developing on one DB and deploying on another with different limits, but that may just be a "enter at your own risk" setup.

• You flagged this item as spam.
  

  Betelgeuse May 20th, 2010 @ 07:22 AM

  There could be a configuration option specifying what all databases will be supported by the project.

• 

  Matt Jones September 21st, 2011 @ 04:13 PM

  • Milestone order changed from “0” to “0”

  (from [2395c8cbb63df80c1cec63ff2ecc3ba05ddf23d6]) [#708] check index name length before creating https://github.com/tablatom/hobo/commit/2395c8cbb63df80c1cec63ff2ec...

• 

  Matt Jones September 21st, 2011 @ 04:15 PM

  • State changed from “open” to “resolved”

  I've added code to 1.3 do the checks. I'm not 100% satisfied with the reporting aspect, as printing to stderr isn't particularly noticeable (especially since the message appears right before the migration preview), but I can't think of any other way to report the issue...