Rails - Apr 2012 - rake db:test:prepare

Why is it necessary for me to run ''rake db:test:prepare'' when
I generate a
new model?

Shouldn''t the ''rake db:migrate'' also affect the test
database? Why would
anyone want to preserve the (broken) state of their test database?

Am I missing something?

-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/lb5AAyOKcMwJ.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.

On Apr 3, 9:43 pm, "@1337807"
<jonanscheff...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> Why is it necessary for me to run ''rake db:test:prepare''
when I generate a
> new model?
>
it shouldn''t be - if you run rake (which defaults to running rake test
or rake spec depending in your setup) it runs rake db:test:prepare for
you
> Shouldn''t the ''rake db:migrate'' also affect the
test database? Why would
> anyone want to preserve the (broken) state of their test database?
>
In general it is easier to clone the test database from the
development database (via schema.rb) than try and replay migrations on
both, particularly for an older application with logs of migrations

Fred

-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.

I do this in my bashrc:

alias migrate=''bundle exec rake db:migrate; RAILS_ENV=test bundle exec
rake db:migrate;''

Not sure of the syntax but you get the idea. I don''t use rake or rake
spec, and prefer running a guard/spork combo. Hence whenever I want to run a
migration, I just run ''migrate'' and that''s it.


Dheeraj Kumar


On Wednesday 4 April 2012 at 3:13 AM, Frederick Cheung wrote:
> 
> 
> On Apr 3, 9:43 pm, "@1337807"
<jonanscheff...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
(http://gmail.com)> wrote:
> > Why is it necessary for me to run ''rake
db:test:prepare'' when I generate a
> > new model?
> > 
> 
> it shouldn''t be - if you run rake (which defaults to running rake
test
> or rake spec depending in your setup) it runs rake db:test:prepare for
> you
> 
> > Shouldn''t the ''rake db:migrate'' also affect
the test database? Why would
> > anyone want to preserve the (broken) state of their test database?
> > 
> 
> In general it is easier to clone the test database from the
> development database (via schema.rb) than try and replay migrations on
> both, particularly for an older application with logs of migrations
> 
> Fred
> 
> -- 
> You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
> To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
(mailto:rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org).
> To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
(mailto:rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org).
> For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
> 
> 

-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.