search for: eager_load

...ort/dependencies.rb:300:in `depend_on'' from /Users/nikosd/.rvm/gems/ree-1.8.7-2011.02@.../gems/activesupport-3.0.5/lib/active_support/dependencies.rb:216:in `require_dependency'' from /Users/nikosd/.rvm/gems/ree-1.8.7-2011.02@.../gems/railties-3.0.5/lib/rails/engine.rb:138:in `eager_load!'' from /Users/nikosd/.rvm/gems/ree-1.8.7-2011.02@.../gems/railties-3.0.5/lib/rails/engine.rb:137:in `each'' from /Users/nikosd/.rvm/gems/ree-1.8.7-2011.02@.../gems/railties-3.0.5/lib/rails/engine.rb:137:in `eager_load!'' from /Users/nikosd/.rvm/gems/ree-1.8.7-2011.02@....

...0.9/lib/active_support/dependencies.rb:304 depend_on at /opt/jruby-1.6.3/lib/ruby/gems/1.8/gems/ activesupport-3.0.9/lib/active_support/dependencies.rb:300 require_dependency at /opt/jruby-1.6.3/lib/ruby/gems/1.8/gems/ activesupport-3.0.9/lib/active_support/dependencies.rb:216 eager_load! at /opt/jruby-1.6.3/lib/ruby/gems/1.8/gems/ railties-3.0.9/lib/rails/engine.rb:138 each at org/jruby/RubyArray.java:1603 eager_load! at /opt/jruby-1.6.3/lib/ruby/gems/1.8/gems/ railties-3.0.9/lib/rails/engine.rb:137 each at org/jruby/RubyArray.java:1603...

....0.3/lib/ active_support/dependencies.rb:300:in `depend_on'' from C:/Ruby187/lib/ruby/gems/1.8/gems/activesupport-3.0.3/lib/ active_support/dependencies.rb:216:in `require_dependency'' from C:/Ruby187/lib/ruby/gems/1.8/gems/railties-3.0.3/lib/ rails/engine.rb:138:in `eager_load!'' from C:/Ruby187/lib/ruby/gems/1.8/gems/railties-3.0.3/lib/ rails/engine.rb:137:in `each'' from C:/Ruby187/lib/ruby/gems/1.8/gems/railties-3.0.3/lib/ rails/engine.rb:137:in `eager_load!'' from C:/Ruby187/lib/ruby/gems/1.8/gems/railties-3.0.3/lib/ ra...

My app works fine in development on my laptop but in production on my server I get "We''re sorry, but something went wrong. We''ve been notified about this issue and we''ll take a look at it shortly." I am using Rails 3, Ruby 1.8.7, Apache and passenger 2.2.15 I get the welcome aboard page in production if I just go to the domain name but as soon as I want data

Hello! Just upgraded to Rails 3.1, ran my test and found this issue: class Trade < ActiveRecord::Base has_many :transaction_trades ..... def Trade.do_something stale_trades = Trade.count(''transaction_trades.id'', :include => :transaction_trades, :group => ''trades.id'')

..._support/dependencies.rb:312:in `depend_on'' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/activesupport-3.2.2/lib/active_support/dependencies.rb:225:in `require_dependency'' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/railties-3.2.2/lib/rails/engine.rb:439:in `block (2 levels) in eager_load!'' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/railties-3.2.2/lib/rails/engine.rb:438:in `each'' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/railties-3.2.2/lib/rails/engine.rb:438:in `block in eager_load!'' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/railties-3.2.2/lib...

...0:in `depend_on'' from /Users/sebastian/.rvm/gems/ruby-1.9.2-p136/gems/activesupport-3.0.3/lib/active_support/dependencies.rb:216:in `require_dependency'' from /Users/sebastian/.rvm/gems/ruby-1.9.2-p136/gems/railties-3.0.3/lib/rails/engine.rb:138:in `block (2 levels) in eager_load!'' from /Users/sebastian/.rvm/gems/ruby-1.9.2-p136/gems/railties-3.0.3/lib/rails/engine.rb:137:in `each'' from /Users/sebastian/.rvm/gems/ruby-1.9.2-p136/gems/railties-3.0.3/lib/rails/engine.rb:137:in `block in eager_load!'' from /Users/sebastian/.rvm/gems/r...

Dear all great developers. I wonder if there is any work being done or thoughts being shared regarding prepared SQL statements. Currently I am in heavy need of tuning SQL INSERTS that insert large (3MB) images into blobs. I am using rails 2.3.5 with postgres adapter and pg driver. Any information would be appreciated. Jarl -- You received this message because you are subscribed to the

Hi, I''ve been trying to get JRuby 1.5.3 with Rails 3 to run on the Tomcat6 server with little success. Has anyone been able to do this? If so, what issues did you have to overcome to get this to work? Also, is this a combination that you would recommend for a production site, or is it all too new and untested? The latest issue I''m stuck on right now is with the mysql-connector-

redux patchset permitting a vm to be associated with multiple networks and vice-versa. updated patchset so as to be applicable against current oVirt server HEAD these patches may be applied in any order, they all need to be pushed together

This patchset contains changes to the ovirt server frontend, backend, and tests components, permitting vms to be associated with multiple networks and vice versa. Also included are two patches which are required for the frontend bits; a patch adding collapsable sections to the vm form, which in itself depends on the second patch that provides default values for the cpu and memory vm table fields

...Proc.new{ |vm| vm.memory_allocated.nil? } - acts_as_xapian :texts => [ :uuid, :description, :vnic_mac_addr, :state ], + acts_as_xapian :texts => [ :uuid, :description, :state ], :terms => [ [ :search_users, 'U', "search_users" ] ], :eager_load => :smart_pools @@ -111,8 +111,8 @@ class Vm < ActiveRecord::Base NEEDS_RESTART_FIELDS = [:uuid, :num_vcpus_allocated, - :memory_allocated, - :vnic_mac_addr] + :memory_allocated] +...