To add to the bikeshet color palette ... On 05.07.2008, at 18:37, Dave Rothlisberger wrote: > rails code). But I feel like I have been battling against the > framework far more than necessary.
As I see it it's an education problem - at least for the examples mentioned. Plugins like better_nested_set are clearly framework level plugins (extending ActiveRecord features). As such they should not make any assumptions about a database being present and it should be possible to implement it like that I guess. *) Also, plugin models that act_as_nested_set cause this problem only if they are loaded during plugin loading time. Avoid that the model is loaded when the plugin's init.rb is loaded and the problem will go away. Again, to me this seems, even if obscure and hard to teach, rather like an education problem (because the plugin has been designed the wrong way) than a problem with rake tasks requiring the environment (which generally makes sense). *) (There are application level plugins out there for which it *might* make sense to make assumptions about the database but they also can't because Rails still has no concept of application level plugins ... but that's a different story ;) -- sven fuchs [EMAIL PROTECTED] artweb design http://www.artweb-design.de grünberger 65 + 49 (0) 30 - 47 98 69 96 (phone) d-10245 berlin + 49 (0) 171 - 35 20 38 4 (mobile) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
