ruby-on-rails-3.2

I have the below association class Picture < ActiveRecord::Base belongs_to :user end class User < ActiveRecord::Base has_many :pictures end And in my PicturesController i am eager loading the user class PicturesController < ApplicationController def index @pictures = Picture.includes(:user).all end end In my view, i am displaying each pictures user name -@pictures.each do |picture| %tr %td= picture.name %td= picture.user.name Now the question is, even though i am eager loading the user, i see individual queries fired while displaying the user name in the view. I have around 1000 picture

I've been searching for a template engine to allow users to create lessons and exercises online easily. Seems like Liquid is the most popular for use in Rails. Can Liquid users easily create rails forms? Normally I create forms in ERB with: <%= form_for(@lesson) do |f| %> <% if @lesson.errors.any? %> <div id="error_explanation"> <h2><%= pluralize(@lesson.errors.count, "error") %> prohibited this lesson from being saved:</h2> <ul> <% @lesson.errors.full_messages.each do |msg| %> <li><%= msg %></li> <% end %> </ul> </div> <% end %> <div>lots of fields</div> <% end %> Rails will automatically

I am using Rails 3.2 serialization to convert ruby object to json. For Example, I have serialized ruby object to following json { "relationship":{ "type":"relationship", "id":null, "followed_id": null } } Using following serialize method in my class Relationship < ActiveRecord::Base def as_json(opts = {}) { :type => 'relationship', :id => id, :followed_id => followed_id } end I need to replace null values with empty strings i.e. empty double quotes, in response json. How can I achieve this? Best Regards, zsquare Probably not the best solution, but inspired by this answer def as_json(opts={})

I'm having a bit of a challenge with understanding accepts_nested_attributes_for. I have a Resident class that is composed of various child classes (address, doctor, guardian, etc). My understanding of the steps necessary to make accepts_nested_attributes_for work is as follows: Create the necessary association(s) Add accepts_nested_attributes_for :resource to the parent class whose form I will use to commit the nested attributes whitelist nested attributes like so. attr_accessible :address_attributes, :doctor_attributes, etc... In the parent controller, build the associated resources. i.e.

Tested on rails 3.2.12 and 3.2.11. In another rails 3.2.11 project I do not have this issue with f.file_field , but in current one I do and can't find a reason for this strange behaviour, so here is my question. I have a weird problem with update action. Here are relevant parts of code: routes: get "signup" => "users#new", :as => "signup" get "profile" => "users#profile", :as => "profile" resources :users do member do get :activate end end controller: def update @user = User.find(params[:id]) if @user.update_attributes(params[:user]) redirect_to user_path(@user), :notice => t('users_controller

I have a nested model form in the style of this Railscast http://railscasts.com/episodes/196-nested-model-form-revised?view=asciicast I need to give each tag a unique ID. Currently, each field generated has a unique ID and name given by a helper method that assigns a unique ID to every association record. So that is taken cared of. However, this form has "fieldset" tags which isn't assigned an ID. I need a unique ID for each fieldset for jQuery manipulation purposes. Specifically, how do I do give each fieldset generated for an "Activity" record a unique CSS tag ID? Posted below is how my form

I know the :: in Ruby is a scope resolution operator to access methods within modules and classes, but is it proper to name classes using :: ? Example class Foo::Bar::Bee < Foo::Bar::Insect def a_method [...] end end If by “proper” you mean syntactically correct — yes . There's nothing inherently wrong with doing it, and if you're defining a subclass in a separate file (example below) then it's a relatively common practice. # lib/foo.rb module Foo end # lib/foo/bar.rb class Foo::Bar end I would avoid defining classes this way if you cannot be sure that the parent module or class already exists

This is my command bundle exec rake resque:work QUEUE="*" --trace I want to run this command on my server as a background process. please help me. A method I often use is: nohup bundle exec rake resque:work QUEUE="*" --trace > rake.out 2>&1 & This will keep the task running even if you exit your shell. Then if I want to just observe trace output live, I do: tail -f rake.out And you can examine rake.out at any time. If you need to kill it before completion, you can find it with ps and kill the pid. Just in case somebody finds this 4 years later, bundle has an elegant way of doing this now. For