Rails Ruby on Rails

Comments and changes to this ticket

• 

  David Trasbo October 9th, 2010 @ 04:20 PM

  • State changed from “new” to “incomplete”
  • Importance changed from “” to “Low”

  Please provide a patch (https://rails.lighthouseapp.com/projects/8994/sending-patches) with a fix and/or a failing test.

• 

  Santiago Pastorino February 2nd, 2011 @ 04:31 PM

  • State changed from “incomplete” to “open”

  This issue has been automatically marked as stale because it has not been commented on for at least three months.

  The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

  Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.

• 

  Santiago Pastorino February 2nd, 2011 @ 04:31 PM

  • State changed from “open” to “stale”

• You flagged this item as spam.
  

  Bogdan Gusiev February 8th, 2011 @ 08:54 AM

  • State changed from “stale” to “open”

  [state:open]

  Yes, I think this is important feature for rails.

  It is connected with production releases and complex migrations when the data should be changed significantly.
  All this process use to fail sometimes.

  In this case if we could rollback the database to the state before migration - we would never have problems with failed deployments.

  Will provide the failing test.

• You flagged this item as spam.
  

  Bogdan Gusiev February 8th, 2011 @ 09:43 AM

  Test and patch.

  • 0001-migrations-make-ddl-transaction-to-rollback-all-migr.patch 4 KB