Jason, how do you avoid the same data migration problems in your gem? If
models you reference in a migration change, the migration would break,
wouldn't it?
Augustin, I find it best to not reference any app models but rather define
new classes for the models I need inside the migration.
On Tue,
You can run migrations one at a time by passing VERSION env variable (see
http://guides.rubyonrails.org/active_record_migrations.html#running-migrations
)
I too see inconsistency here. I wish all operations supported both STEP and
VERSION.
On Sun, Mar 29, 2015 at 6:23 PM, Michael Mahemoff
I think STEP parameter is what you're looking for:
http://guides.rubyonrails.org/migrations.html#rolling-back
On Thu, Feb 13, 2014 at 3:36 PM, HariHaraSudhan KM
km.hariharasud...@gmail.com wrote:
Hi people,
I found it a little hard to migrate up,down,redo with version
numbers, i
It sounds like an interesting idea but I have some concerns. How about
value stored in AR instance? You wouldn't know what value was saved to
database unless you reload the record.
Pranas
On Tuesday, January 22, 2013 8:15:16 AM UTC-8, ChuckE wrote:
I understand what you mena. However, how
