Home
7 items | 60 visits
-
ActiveRecord
-
The case for piggy backed attributes
-
Add Sticky Note
-
This is a feature of the Active Record ORM mapping that I like very much, because it can be used to speedup you queries enormously.
-
-
The beauty of a nested ':include' option [rails] [rubyonrails] [relationships] [associations] [activerecord]
-
So you've got a lot of stuff, spread over a lot of tables, and now you want to scoop it all up and display it all in the same view - oh, and you don't want ActiveRecord to perform a bazillion subsidiary SQL lookups along the way. The answer - a nested :include clause.
-
-
cfis : Making Rails Go Vroom
-
- Don't use ActiveRecord#attributes
- Get your :includes right
- Don't check template timestamps ( cache_template_loading = true)
- Don't use url_for
- Don't let Rails parse timestamps
- Don't symbolize keys (local_assigns_support_string_keys = false)
-
Add Sticky NoteSo, any place we access times, we simply roll our own attribute readers and writers like this (note that we don't use read_attribute!).
-
-
Ruby: Date / Rational / Fixnum#gcd hack increased app performance by 15% | Kurt Stephens
-
Ruby
DateusesRationalheavily, which callsInteger#gcdfor every newRational. TheInteger#gcdmethod is generic to handleBignums, but performs terribly forFixnum#gcd(Fixnum), which is probably the most often case.
-
-
RailsLodge - Acts As Modified plugin
-
This plugin lets you track attribute changes to an ActiveRecord object.
-
-
Terralien - QueryTrace
-
QueryTrace is a Rails plugin for pinpointing where in your Rails application that slow query is running. While ActiveRecord takes you half-way there by logging all queries and how long they’re taking, it won’t answer the question of where they’re being executed. Enter QueryTrace – once you have it installed, your logs won’t just tell you that you have a problem, they will pinpoint the exact location of that problem for you.
-
1 - 7 of 7
Showing 20▼ items per page
List Comments
(0)
List Info
Sponsored Links
Ads by Google