Pretty interesting! I misread the output. In fact, my output is like
yours. I didn't see "db:setup" (which I wrongly called "db:load")
before. But, as you can see, "db:reset" only shows up mentioned in
"db:setup".
It is not possible to "rake -D db:reset", for instance.
That is what first called my attention and then I was fast on my wrong
conclusions ;)
Thank you,
Rodrigo.
Em 04-03-2011 11:36, Prem Sichanugrist escreveu:
Hi Rodrigo,
I cannot reproduce your problem on latest 3.0.5. Here's my gist
showing the test: https://gist.github.com/854691
- Prem
On 4 มี.ค. 2554, at 21:14, Rodrigo Rosenfeld Rosas wrote:
Is there any reason why db:setup and db:reset don't show any more on
"rake -T db"?
I guess any rake task that is defined only as a group of other tasks
(without any ruby blocks attached) presents this problem.
Also let me write this as a remember note to myself for when I have
some time: the Rails Guides on Migrations should be updated to
include instructions about db:load and to add the information that
it, alongside with "db:reset", also loads the seed data after
(re)creating the database from schema.rb.
Rodrigo.
--
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Core" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
