Skip to content

Commit

Permalink
Remove some entries from the 4.0 release notes
Browse files Browse the repository at this point in the history
We need more ❤️ in this file. There are a lot of outdated entries.
  • Loading branch information
rafaelfranca committed Aug 26, 2012
1 parent e6e5898 commit df1d21a
Showing 1 changed file with 0 additions and 25 deletions.
25 changes: 0 additions & 25 deletions guides/source/4_0_release_notes.textile
Expand Up @@ -479,35 +479,10 @@ end
User.stored_attributes[:settings] # [:color, :homepage] User.stored_attributes[:settings] # [:color, :homepage]
</ruby> </ruby>


* <tt>composed_of</tt> was removed. You'll have to write your own accessor and mutator methods if you'd like to use value objects to represent some portion of your models. So, instead of:

<ruby>
class Person < ActiveRecord::Base
composed_of :address, :mapping => [ %w(address_street street), %w(address_city city) ]
end
</ruby>

you could write something like this:

<ruby>
def address
@address ||= Address.new(address_street, address_city)
end

def address=(address)
self[:address_street] = @address.street
self[:address_city] = @address.city

@address = address
end
</ruby>

* PostgreSQL default log level is now 'warning', to bypass the noisy notice messages. You can change the log level using the <tt>min_messages</tt> option available in your <tt>config/database.yml</tt>. * PostgreSQL default log level is now 'warning', to bypass the noisy notice messages. You can change the log level using the <tt>min_messages</tt> option available in your <tt>config/database.yml</tt>.


* Add uuid datatype support to PostgreSQL adapter. * Add uuid datatype support to PostgreSQL adapter.


* <tt>update_attribute</tt> has been removed. Use <tt>update_column</tt> if you want to bypass mass-assignment protection, validations, callbacks, and touching of updated_at. Otherwise please use <tt>update_attributes</tt>.

* Added <tt>ActiveRecord::Migration.check_pending!</tt> that raises an error if migrations are pending. * Added <tt>ActiveRecord::Migration.check_pending!</tt> that raises an error if migrations are pending.


* Added <tt>#destroy!</tt> which acts like <tt>#destroy</tt> but will raise an <tt>ActiveRecord::RecordNotDestroyed</tt> exception instead of returning <tt>false</tt>. * Added <tt>#destroy!</tt> which acts like <tt>#destroy</tt> but will raise an <tt>ActiveRecord::RecordNotDestroyed</tt> exception instead of returning <tt>false</tt>.
Expand Down

0 comments on commit df1d21a

Please sign in to comment.