Ruby on Rails Tuesday, September 5, 2017

-----BEGIN PGP SIGNATURE-----

iQJIBAEBCAAyFiEEN3gQFkOJVa2DePULsxg2h+KO4AcFAlmuyoAUHHRpbW1lbHpl
ckBnbWFpbC5jb20ACgkQsxg2h+KO4Afqow/8CJh9962ogibN5UnQdH7Gk5cF4s3/
il4LO8ydnil3F4Cbli4Xh0SQdHzCzWSo90otTe99YVnoOuI/OvWbe80s/f2iEchJ
Q4qIhGtI0jej7Oz9ul0blq4hIp2hPpECwUGUkmlmM3YS/ti0ESf8IvEdalbkuNWP
vzQScOqpGamoU/LxreFsiaKfL8HcHrSXCu6jaWPngsiNJWLhhdpnlVRF6Li7EXP4
OJ4Oo/akgNZJCbGXnuk0gC3Lj+ESlKzag1R+522Pl0WlwvpJoRjFkExvOg4reuNA
Y5xjQgF8CwbVZh6lWzmjRXJDIBMSiyGbnqdoEbWmZN86Iqj/6FcEkgbDMogyW+KR
r0pNzw0vdSEvQzeo0vzR4WBLAx174dHhHXJLu9SiQDGISaWvVZz7R2g98tSbzcXh
o6pr2nhS4wa0vQj8zmUohctAYjW6A/UF+qjRg/HTIGJ2IXbG3hh1hgCR/J67q2Le
HBsClTGZR1AsTECTXes1M4mXwsMiwk6Rw4R/yl49JxJWz0OEcF8BDoRarx0ISINZ
QfspLA5YQPfZhHlhdn97JnFsEzTNGMWyZZXh3O/qwXLWp1pz+t4sNw40RHNZp0iV
btwg6/DICs9goNyHgxVbDjQMtIQ8u11m8CPgP/MSHTosIkJ1/7rGAj1QkuePMFoo
AAcWDBM4eBFznJ0=
=GAdK
-----END PGP SIGNATURE-----
On 09/05/2017 05:51 PM, Joe Guerra wrote:
> the database isn't in production, it has a bunch of faker data in it.

I do not care… You are taking huge risks by changing old migrations and
re-running from scratch. This way you might have deleted to much and
therefore your model might get out of sync with the table.

While when you add a single migration which is responsible to clean up
your schema, you can easily roll it back if you realise that it didn't
work as expected. This way back is not easily possible when you alter
your migrations history.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/4f3e88cf-8614-8aca-a614-9308eb653b34%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment