Some odd false alarm, it wasn't actually broken. Sorry.
Michael Schoen wrote:
"david" made AR/Oracle cry...
http://dev.rubyonrails.org/changeset/4197
r4197 | david | 2006-04-07 11:21:52 -0700 (Fri, 07 Apr 2006) | 1 line
F
Now that Rails has a stable branch, I would like to suggest considering using
svnmerge.py to manage the revisions in trunk that you want to pull over into the
branch. It'll make life much easier in managing commits to trunk and then
merging them to stable.
Svnmerge.py makes life easy in migra
"david" made AR/Oracle happy again, thank you!
http://dev.rubyonrails.org/changeset/4199
r4199 | david | 2006-04-07 11:29:43 -0700 (Fri, 07 Apr 2006) | 1 line
RAILS_ROOT, please
--
"david" made AR/Oracle cry...
http://dev.rubyonrails.org/changeset/4197
r4197 | david | 2006-04-07 11:21:52 -0700 (Fri, 07 Apr 2006) | 1 line
Fixed that boot.rb would set RAILS_GEM_VERSION twice, not respect an
uncommented
Hi Chris,
This doesn't really belong on core but I can point you to an alternative
solution to prevent the FULL table update. While your solution is
imaginative, the fact that it doesn't scale sinks the boat.
http://www.railtie.net/articles/2006/03/31/implement-acts_as_threaded-withou
t-a-plugin
