James Mason fa55224163 Break up the one-query-of-doom ... The single query was producing a tremendously large ActiveRecord allocation. While this isn't nearly as cool as one query, it's still a significant reduction in SQL trips, and now has the bonus of only loading what is actually going to be displayed.		2017-12-22 10:48:55 -08:00
..
base_controller_spec.rb
campaign_spec.rb
cfp_ability_spec.rb
cfp_spec.rb
commercials_spec.rb
conference_registration_spec.rb
conference_spec.rb
contact_spec.rb
difficulty_levels_spec.rb
email_spec.rb
event_types_spec.rb
info_desk_ability_spec.rb
lodgings_spec.rb
omniauth_spec.rb
organization_admin_ability_spec.rb
organization_spec.rb
organizer_ability_spec.rb
program_spec.rb
proposals_spec.rb
registration_periods_spec.rb
resource_spec.rb
roles_spec.rb
rooms_spec.rb
splashpage_spec.rb	Break up the one-query-of-doom	2017-12-22 10:48:55 -08:00
sponsor_spec.rb
sponsorship_level_spec.rb
ticket_purchases_spec.rb
tickets_spec.rb
track_organizer_ability_spec.rb
tracks_spec.rb
user_ability_spec.rb
user_spec.rb
venues_spec.rb
versions_spec.rb	Break up the one-query-of-doom	2017-12-22 10:48:55 -08:00
volunteers_spec.rb