On Aug 18, 12:33 am, Tomasz Romanowski wrote:
> > Rails comes with 3 development environments already ready to go, look
> > database.yml. In development and testing, all classes are always
> > reloaded.
>
> This does not seem to be true. In my example above, if a class does not
> derive from Ac
On Mon, Aug 16, 2010 at 7:10 PM, Tomasz Romanowski wrote:
> Yep, that's it, thanks. Makes me wonder how I can control which classes
> should be reloaded. I'm trying to make something off of development.rb
> and production.rb.
Rails comes with 3 development environments already ready to go, look
d
>> Most classes in your app are reloaded between requests. Is this the
>> problem ?
>
> To clarify, that of course only happens in development
>
Yep, that's it, thanks. Makes me wonder how I can control which classes
should be reloaded. I'm trying to make something off of development.rb
and pr
On Aug 16, 4:23 pm, Frederick Cheung
wrote:
> On Aug 16, 3:48 pm, Tomasz Romanowski wrote:
>
> > I have two classes with class variables. One of them derives from active
> > record, the other one does not. I initialize both members to NULL, then
> > lazy-instantiate them. The class which does n
On Aug 16, 3:48 pm, Tomasz Romanowski wrote:
> I have two classes with class variables. One of them derives from active
> record, the other one does not. I initialize both members to NULL, then
> lazy-instantiate them. The class which does not derive from active
> record preserves the value corr
5 matches
Mail list logo