More Cowbell

Standup 07/19/2008

edit Posted by Joe Moore on Friday July 18, 2008 at 08:57PM

Interesting Things

Firebug 1.1.0.b12 is EVIL!

Watch out for Firebug 1.1.0b12 for Firefox 2! It is The Evil. Several hours have been wasted as teams try to figure out what they are doing wrong ("Why are all of the fonts twice as big?!?!") only to find out that this version of Firebug was the culprit.

To fix:

Uninstall Firebug from the Tools - Add-ons menu
Restart Firefox. Do not skip this step!
Install Firebug 1.0.5

Standup Free Slurpee! 07/11/2008

edit Posted by Joe Moore on Friday July 11, 2008 at 04:50PM

Standup fun-stuff edition!

Interesting Things

Free Slurpee Day! Head to 711 Market Street (oh yeah) for a brain freeze.

Where are all of the Pivots? Hmmm...

Pie and brownies for breakfast!
Pivot Jonathan's wife is having an art opening. Check it out the Glass Cafe at Public Glass, Saturday, July 12, 6-9pm.

Pivot David band Gosta Berling is playing at Mr. Smith's at 7th. and Market St. on 07/17.

Ask for Help

"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.

Standup 07/10/2008

edit Posted by Joe Moore on Thursday July 10, 2008 at 07:58PM

Update 07/11/2008: A fix has been committed for the :named_scope_-column-collision issue.

Interesting Things

In Rails 2.0.2, we have seen a strange behavior when you have a 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.
When using 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.
We ran into an issue when using the JS Routes plugin in combination with Rails' asset packaging. When asset packaging is invoked using <%= 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.

Ask for Help

"Why did my JS respond_to block 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.