resolve/refinerycms-inquiries — comment on commit a971e7db0050d0c63a51dea3f298e163953f0c2d
File:  line 0
By dmoose:

At a minimum we need to get an upgrade doc going with gotchas like this
in it. This one could have been handled with a test for the old table
and a rename as part of the new migration. It could be removed
eventually, but for the short run it would be worth it. I'm guessing a
lot of upgrade issues can't be handled so easily, but something needs to
be done to help migrate live edge sites to the new release.

Devise 2.0 had multiple incompatible changes and they were handled with
deprecation warnings. Something as fundamental as renaming tables would
certainly merit a deprecation warning rather than silent fail.

On 2/21/2012 4:12 PM, Philip Arndt wrote:
> Honestly I'm not sure currently how you would upgrade, and I'm unhappy
> about this :(
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/resolve/refinerycms-inquiries/commit/a971e7db0050d0c63a51dea3f298e163953f0c2d#commitcomment-993821
>