Notes

I am sure others have tried to do this but I thought I would add a not that tells ever one. You can't use the type field in in rails 2.3. It is always set back to type => "text"

So if you are trying to set it to type => "number" it will not work. It always goes back to text. Sorry only way around t...

The <% -%> is not being used since Rails 3.

The example above should be changed to:

<%= form_tag('/posts') do %>
<div><%= submit_tag 'Save' %></div>
<% end %>

The stacking of several after_commit lines is not working.
The last line overwrites the ones before.

Using an array for the :on options is also not working.

For details look here:
http://github.com/rails/rails/issues/988#issuecomment-12653474

:fav_bra_size - really?

You have explain well about fragment caching as I was in need of this information. http://autobodycarparts.com

Thanks for the coding part it was really helpful for me, I would apply it on my project. http://www.koolchart.com

You can update multiple attributes with sql for each record being updated by using the following syntax:

==== example

Model.update_all("foo = 'bar', baz = 'bat'")

This example shows how to use find_index to return a result as soon as the first occurrence of what you are looking for is found.

==== Code example
class Widget < Struct.new(:name, :profit); end

class WidgetManager
def initialize(*widgets)
  @widgets = widgets
end
def...

==== This Worked For Me

require File.expand_path('../app/models/extenstions/active_record_ext', File.dirname(FILE))

I did this in application.rb

The deprecated function (http://apidock.com/rails/ActiveRecord/Serialization/to_json) has more useful documentation for the options hash.

NilClass#try doesn't check for methods on itself: nil.blank? #=> true nil.try :blank? #=> nil

touch is used to update the updated_at column you can create a model instance and update the updated_at value on it

Let say we have one user model

user = User.first

next you can write

user.touch

so it will run the query for you

UPDATE users SET updated_at = 'current_date_time' WHERE `user...

==== Code example # Remove empty strings { a: 'first', b: '', c: 'third' }.reject { |k,v| v.empty? } #=> {:a=>"first", :c=>"third"}

# Remove nil
{a: 'first', b: nil, c: 'third'}.reject { |k,v| v.nil? } # => {:a=>"first", :c=>"third"}

# Remove nil & empty strings
{a: '', b:...

We can use hash#slice[http://api.rubyonrails.org/classes/Hash.html#method-i-slice] if we want an Hash#extract (without bang) like behavior.

@concept47 do you really need to check the fragment in the controller?

ActiveRecord will execute the query when its used

cars = Car.where(:colour => 'black') # No Query cars.each {|c| puts c.name } # Fires "select * from cars where ..."

"Lazy Loading" - http://m.onkey.org/active-record-que...

Olefine, I'm not sure here is a good place for such questions (better use stackoverflow for example), but answer for your question is that Rails provide slice (and many other methods) not only for Hash class but for HashWithIndifferentAccess too such as for any other superclass of Hash, so they use...

it will use all the field related to particular table so you can find data by any table field like Table name => ABC(:id, :name, :address) if you want to find data related to id or name or address than only write

ABC.find_by_id(1)

ABC.find_by_name("abc")

ABC.find_by_address("abc")

find_by_field...

You can actually pass in an expires_in option that sets how long Rails should show the fragment before deleting it so as an example ...

<% cache('homepage_sidebar', :expires_in => 10.minutes) do %>
<div>
  ...
</div>
<% end %>

This only used to work with memcached but it now w...

Why it use? hash = self.class.new Instead it, we may use hash = {}

Just an FYI, this is not supported on Memcached, so I would avoid it if you're using FileStore and are planning on moving over to Memcached eventually.