This project is archived and is in readonly mode.
Migration doesn't update scaffold-generated fixture
Reported by François ANTIER | March 26th, 2009 @ 07:33 AM | in 2.x
The title says it all...
To reproduce it: - create a new table using the scaffold generator - write a migration that removes one of the table columns - apply that migration - the fixture test for that column isn't updated.
Comments and changes to this ticket
-
François ANTIER March 26th, 2009 @ 07:57 AM
- Title changed from “"remove_column" in migration does not remove entry in scaffold-generated fixture” to “Migration doesn't update scaffold-generated fixture”
Applying a migration wih 'add_column' or 'remove_column' does not add or remove the field entry in the corresponding, scaffold-generated fixture.
I'm not sure whether scaffold-generated files are normally kept in sync later... I've run into a few other similar issues before. What do you think ?
-
CancelProfileIsBroken March 26th, 2009 @ 10:55 AM
- State changed from “new” to “invalid”
By design. Fixtures don't get resynched after creation. Feel free to patch.
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>
CancelProfileIsBroken