“How can I make follow_redirect go to a URL?”
When using a follow_redirect to a URL instead of a hash, the test fails with a string conversion exception. No solutions were forthcoming.
Standup fun-stuff edition!
“Sometimes
find(:first, :order => 'id DESC')returns the records in the wrong order!”
Rails 2.0.2. Roughly 1 out of every 15 times, the first id is not the first one returned. Very very strange.
Update 07/11/2008: A fix has been committed for the :named_scope_-column-collision issue.
belongs_to association declared on an ActiveRecord class, but the table does not have a foreign key for that relationship. Within a session, everything appears normal. The child object will still be saved, the parent object can even be reloaded. But by the next session, the child object is in the database, but cannot be retrieved.named_scope, adding a :joins option will “mix-in” all of the attributes from that join table into your retrieved object, potentially overwriting any colliding attributes (including id … ouch!). There was consensus that this was a valuable feature, when used “properly”. Adding :select option can avoid this, or use :include.<%= javascript_include_tag 'named_routes', 'xxx', :cache => true %> the named_routes.js file usually has not been generated, and application crashes at startup. Solution: we created a rake task to generate the named_routes.js file and run that as part of our deploy process.“Why did my JS
respond_toblock suddenly start rendering the HTML template instead of the RJS template?”
Rails 2.0.2; controller, action, respond_to block all work as expected. Just wrong file gets rendered. They fixed the problem by adding an explicit call to render but this should not be necessary. Suggestion is to move from the template.rhtml naming scheme to template.mime-type.render-engine scheme and see if it is fixed.
“When monit kills our Mongrels, our in-progress transactions are committed, not rolled-back!”
This is with Rails 1.99. Has anyone heard of this?
“Does anyone have suggestions for debugging Safari-specific JavaScript problems?”
Suggestion: download the nightly build of Safari/WebKit, which has a real JavaScript debugging tool.
“After switching from Selenium RC Fu to Polonium, our Selenium tests run extremely slow.”
The affect is similar to Selenium’s slow-mode.
ActiveRecord’s #method_missing takes precedence over private methods, which means you cannot simply mark “private” database-derived attributes.
code:
# File: app/models/rock_star.rb
#
# == Schema Information
# Schema version: 1
#
# Table name: rock_stars
#
# id :integer not null, primary key
# real_name :string(255)
# band_name :string(255)
# personal_life :string(255)
#
class RockStar < ActiveRecord::Base
def method_missing(method, *arguments, &block)
puts "I see you've sent my #{method} back and my ActiveRecords and they're all scratched"
super
end
private
def personal_life=(arg)
puts "Vanish in the air you'll never find me"
attributes[:personal_life] = arg
end
end
script/console:
Loading development environment (Rails 2.0.2)
>> sting = RockStar.new(:real_name => 'Gordon Sumner', :band_name => 'The Police')
I see you've sent my real_name= back and my ActiveRecords and they're all scratched
=> #<RockStar id: nil, real_name: "Gordon Sumner", band_name: "The Police", personal_life: nil>
>> sting.personal_life = "I'll be watching you"
I see you've sent my personal_life= back and my ActiveRecords and they're all scratched
=> "I'll be watching you"
Potential solutions:
Exception:
class RockStar < ActiveRecord::Base
def personal_life=(arg)
raise "Protest is futile, nothing seems to get through"
end
end
Have another? Post a comment.
||= (”or equal”) blows up you have a public “writer”, but a private “reader”; makes sense, but still worth a mention.
code:
class Model < ActiveRecord::Base
def field_name=(arg)
@field_name = arg
end
private
def field_name
@field_name
end
end
script/console:
Loading development environment (Rails 2.0.2)
>> instance = Model.new
=> #<Model id: nil, field_name: nil>
>> instance.field_name = 'lala'
=> "lala"
>> instance.field_name ||= 'dodo'
NoMethodError: private method `field_name' called for #<Model:0x17df6d0>
from /Library/Ruby/Gems/1.8/gems/activerecord-2.0.2/lib/active_record/attribute_methods.rb:205:in `method_missing'
from (irb):4
ActiveRecord writers always return the passed in argument, even if you define some other return value. This also makes sense — necessary for chaining, etc., but what the heck…
code:
class Model < ActiveRecord::Base
def field_name=(arg)
@field_name = arg
return "custom return value"
end
end
script/console:
Loading development environment (Rails 2.0.2)
>> instance = Model.new
=> #<Model id: nil, field_name: nil>
>> instance.field_name = 'lala'
=> "lala"
We’ve decided to share Tracker with the agile community. Details of the launch have yet to be worked out, including an exact date, but please register here if you’re interested in participating in the beta.
Stay tuned for more details!
Note: attr_readonly was either buggy or not exposed prior to 1.2.3. If you are using a version of rails prior to 1.2.3 you can do this instead:
def attributes_with_quotes(include_primary_key = true)
attributes.inject({}) do |quoted, (name, value)|
if column = column_for_attribute(name)
# original:
# quoted[name] = quote_value(value, column) unless !include_primary_key && column.primary
quoted[name] = quote_value(value, column) unless !include_primary_key &&
(column.primary || ["your_attributes", "listed_here"].include?(column.name))
end
quoted
end
end