From c70b993a9e01547de88417cb8fa95b48acbed2db Mon Sep 17 00:00:00 2001 From: Pratik Naik Date: Fri, 14 Nov 2008 17:47:21 +0530 Subject: Merge docrails. --- railties/doc/guides/html/2_2_release_notes.html | 33 +++++++++++++++++++++---- 1 file changed, 28 insertions(+), 5 deletions(-) (limited to 'railties/doc/guides/html/2_2_release_notes.html') diff --git a/railties/doc/guides/html/2_2_release_notes.html b/railties/doc/guides/html/2_2_release_notes.html index 931786ef6c..e79f7ec511 100644 --- a/railties/doc/guides/html/2_2_release_notes.html +++ b/railties/doc/guides/html/2_2_release_notes.html @@ -243,6 +243,8 @@ ul#navMain {
  • Method Arrays for Member or Collection Routes
    • +
  • Resources With Specific Actions
    • +
  • Other Action Controller Changes
    • @@ -525,7 +527,7 @@ More information :

    There are two big additions to talk about here: transactional migrations and pooled database transactions. There's also a new (and cleaner) syntax for join table conditions, as well as a number of smaller improvements.

    5.1. Transactional Migrations

    -

    Historically, multiple-step Rails migrations have been a source of trouble. If something went wrong during a migration, everything before the error changed the database and everything after the error wasn't applied. Also, the migration version was stored as having been executed, which means that it couldn't be simply rerun by rake db:migrate:redo after you fix the problem. Transactional migrations change this by wrapping migration steps in a DDL transaction, so that if any of them fail, the entire migration is undone. In Rails 2.2, transactional migrations are supported on PostgreSQL only. The code is extensible to other database types in the future.

    +

    Historically, multiple-step Rails migrations have been a source of trouble. If something went wrong during a migration, everything before the error changed the database and everything after the error wasn't applied. Also, the migration version was stored as having been executed, which means that it couldn't be simply rerun by rake db:migrate:redo after you fix the problem. Transactional migrations change this by wrapping migration steps in a DDL transaction, so that if any of them fail, the entire migration is undone. In Rails 2.2, transactional migrations are supported on PostgreSQL out of the box. The code is extensible to other database types in the future - and IBM has already extended it to support the DB2 adapter.

    @@ -693,9 +700,9 @@ Counter cache columns (for associations declared with :counter_cache ⇒

    6. Action Controller

    -

    On the controller side, there are a couple of changes that will help tidy up your routes.

    +

    On the controller side, there are several changes that will help tidy up your routes. There are also some internal changes in the routing engine to lower memory usage on complex applications.

    6.1. Shallow Route Nesting

    -

    Shallow route nesting provides a solution to the well-known difficulty of using deeply-nested resources. With shallow nesting, you need only supply enough information to uniquely identify the resource that you want to work with - but you can supply more information.

    +

    Shallow route nesting provides a solution to the well-known difficulty of using deeply-nested resources. With shallow nesting, you need only supply enough information to uniquely identify the resource that you want to work with.

    +
    map.resources :photos, :only => [:index, :show]
+map.resources :products, :except => :destroy
+
    +
    +

    6.4. Other Action Controller Changes

    • -- cgit v1.2.3 From ad679a43ec288610088d82b3cbd4009646ebde17 Mon Sep 17 00:00:00 2001 From: Pratik Naik Date: Fri, 14 Nov 2008 20:32:33 +0530 Subject: Update release notes from docrails. --- railties/doc/guides/html/2_2_release_notes.html | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) (limited to 'railties/doc/guides/html/2_2_release_notes.html') diff --git a/railties/doc/guides/html/2_2_release_notes.html b/railties/doc/guides/html/2_2_release_notes.html index e79f7ec511..68b8188f7c 100644 --- a/railties/doc/guides/html/2_2_release_notes.html +++ b/railties/doc/guides/html/2_2_release_notes.html @@ -812,6 +812,16 @@ Rails now supports HTTP-only cookies (and uses them for sessions), which help mi render now supports a :js option to render plain vanilla javascript with the right mime type.

      • +
    • +

      +Request forgery protection has been tightened up to apply to HTML-formatted content requests only. +

      +
      • +
    • +

      +Polymorphic URLs behave more sensibly if a passed parameter is nil. For example, calling polymorphic_path([@project, @date, @area]) with a nil date will give you project_area_path. +

      +

    7. Action View

    @@ -856,6 +866,7 @@ More information: +

    Action Mailer now offers built-in support for GMail's SMTP servers, by turning on STARTTLS automatically. This requires Ruby 1.8.7 to be installed.

    9. Active Support

    @@ -1094,7 +1105,7 @@ Wrapped Rails.env in StringInquirer so you can do Rails.en

  • -script/generate works without deprecation warnings when RubyGems 1.3.0 is present +To eliminate deprecation warnings and properly handle gem dependencies, Rails now requires rubygems 1.3.1 or higher.

    • -- cgit v1.2.3