Forum: Ruby on Rails Class caching yields the wrong data

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
D68c97e8e2f1653b54c24493caf236ae?d=identicon&s=25 (Guest)
on 2007-07-17 03:40
(Received via mailing list)
In production (and in development, with environment config set to
"config.cache_classes = true"), sometimes the wrong object is
associated with the wrong object because of caching.

I'd rather, however, not take a performance hit by turning caching
completely off.

Is there a way to force a class to reload?  I've tried using "reload"
and "clear_reloadable_connections!()" ...but perhaps I'm not using
them correctly.

This topic is locked and can not be replied to.