This project is archived and is in readonly mode.
model only rake environment
Reported by gaffo | December 16th, 2008 @ 01:26 AM | in 2.x
With the introduction of cache_classes, rake tasks can now be caching the models, controllers, and helpers.
It would be nice to have different levels of the environment rake dependency that loaded different levels of these such that things like db:migrate would only have to load up the models, not the entire tree.
This would speed up many of the rake tasks' startup time. In a large application this makes a decent different in rapid development.
Having controllers load before migrations happen can also cause chicken and egg problems with controllers seeking out table info on initialization purposes for caching purposes when they weren't expecting to be loaded.
Comments and changes to this ticket
-
gaffo December 16th, 2008 @ 02:28 PM
In light of 802, this one could be when the solution for #802 allows db:migrate* to run without caching classes.
-
Jeremy Kemper December 16th, 2008 @ 10:18 PM
- State changed from new to duplicate
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>