#788 Migration generator should check if name collides with existing class - Hobo

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

#788 open

Migration generator should check if name collides with existing class

Reported by Betelgeuse | September 7th, 2010 @ 02:02 PM | in Hobo 1.4

Migration will not work if you name the migration class with the same name as an existing Hobo model. The migration generator should check if a class with that name already exists and ask the user the provide a new name.

Comments and changes to this ticket

Matt Jones September 14th, 2011 @ 09:29 PM
- State changed from “new” to “open”
- Milestone set to “Hobo 1.4”
- Milestone order changed from “197880” to “0”
Note that the underlying Rails code already checks for duplicate migration names, but not for this situation.
Matt Jones September 20th, 2011 @ 05:08 PM
(from [2367f9f15416d19b2682a80e6c8dfed8156ee326]) [#788] indicate disabled buttons https://github.com/tablatom/hobo/commit/2367f9f15416d19b2682a80e6c8...

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.