<?xml version="1.0" encoding="UTF-8"?>
<user>
  <id type="integer">243399</id>
  <url>http://uservoice.com/users/243399-noahhorton</url>
  <avatar_url>http://www.gravatar.com/avatar/24e3e673f6cd686942225eeec6a4ed72?default=http://uservoice.com/images/icons/default-avatar.jpg</avatar_url>
  <display_name>NoahHorton</display_name>
  <name deprecated="true">NoahHorton</name>
  <username deprecated="true">NoahHorton</username>
  <activity_score type="integer">0</activity_score>
  <idea_score type="integer">0</idea_score>
  <supported_suggestions type="array" deprecated="false">
<suggestion>
  <id type="integer">98450</id>
  <url>http://rails.uservoice.com/pages/10012-rails/suggestions/98450-try-to-merge-all-the-rails-doc-apps</url>
  <title>try to merge all the rails-doc apps</title>
  <abstract>There are now a lot of web-apps concerned with showing/improving the Rails documentation. It would be great if the community could focus on one of these. This app should then become the official...</abstract>
  <text>There are now a lot of web-apps concerned with showing/improving the Rails documentation. It would be great if the community could focus on one of these. This app should then become the official api-resource for Rails and replace api.rubyonrails.com</text>
  <closed_at nil="true"></closed_at>
  <vote_count type="integer">102</vote_count>
  <comments_count type="integer">1</comments_count>
  <status>under review</status>
  <forum>
    <id type="integer">10012</id>
    <name>Rails</name>
    <key deprecated="true">rails3</key>
  </forum>
  <response nil="true"></response>
  <created_by>
    <supporter>
      <user>
        <id type="integer">199821</id>
        <display_name>anonymous</display_name>
        <name deprecated="true">anonymous</name>
        <username deprecated="true">anonymous</username>
      </user>
    </supporter>
  </created_by>
  <created_at type="datetime">2009-01-05T18:30:14Z</created_at>
  <updated_at type="datetime">2009-03-11T20:28:19Z</updated_at>
  <page deprecated="true">
    <key>rails3</key>
  </page>
</suggestion>
<suggestion>
  <id type="integer">107607</id>
  <url>http://rails.uservoice.com/pages/10012-rails/suggestions/107607-have-a-standard-async-api</url>
  <title>Have a standard async API</title>
  <abstract>Everyone and their brother has implemented an asynchronous processing system for rails now.  90% of them don't work well, and they all have different interfaces.  

Lets minimally standardize an...</abstract>
  <text>Everyone and their brother has implemented an asynchronous processing system for rails now.  90% of them don't work well, and they all have different interfaces.  

Lets minimally standardize an interface so that we can plug different implementations in without changing app code, and preferably have a good reference implementation.</text>
  <closed_at nil="true"></closed_at>
  <vote_count type="integer">12</vote_count>
  <comments_count type="integer">1</comments_count>
  <status nil="true"></status>
  <forum>
    <id type="integer">10012</id>
    <name>Rails</name>
    <key deprecated="true">rails3</key>
  </forum>
  <response nil="true"></response>
  <created_by>
    <supporter>
      <user>
        <id type="integer">221412</id>
        <display_name>nhorton</display_name>
        <name deprecated="true">nhorton</name>
        <username deprecated="true">nhorton</username>
      </user>
    </supporter>
  </created_by>
  <created_at type="datetime">2009-01-21T22:46:28Z</created_at>
  <updated_at type="datetime">2009-01-21T22:46:28Z</updated_at>
  <page deprecated="true">
    <key>rails3</key>
  </page>
</suggestion>
<suggestion>
  <id type="integer">107612</id>
  <url>http://rails.uservoice.com/pages/10012-rails/suggestions/107612-have-r-w-db-partitioning-support</url>
  <title>Have R/W DB partitioning support</title>
  <abstract>The only way of using R/W DB partitioning that I know of with Rails that does not require a lot of code modification is using mysql-proxy, which is obviously limited to MySQL.  This should be...</abstract>
  <text>The only way of using R/W DB partitioning that I know of with Rails that does not require a lot of code modification is using mysql-proxy, which is obviously limited to MySQL.  This should be supported in ActiveRecord at a deeper level.</text>
  <closed_at nil="true"></closed_at>
  <vote_count type="integer">3</vote_count>
  <comments_count type="integer">0</comments_count>
  <status nil="true"></status>
  <forum>
    <id type="integer">10012</id>
    <name>Rails</name>
    <key deprecated="true">rails3</key>
  </forum>
  <response nil="true"></response>
  <created_by>
    <supporter>
      <user>
        <id type="integer">221412</id>
        <display_name>nhorton</display_name>
        <name deprecated="true">nhorton</name>
        <username deprecated="true">nhorton</username>
      </user>
    </supporter>
  </created_by>
  <created_at type="datetime">2009-01-21T22:49:41Z</created_at>
  <updated_at type="datetime">2009-01-21T22:49:41Z</updated_at>
  <page deprecated="true">
    <key>rails3</key>
  </page>
</suggestion>
<suggestion>
  <id type="integer">107617</id>
  <url>http://rails.uservoice.com/pages/10012-rails/suggestions/107617-auto-render-partials</url>
  <title>Auto-render partials</title>
  <abstract>The same way that link_to can infer the URL you want just by passing it objects (assuming you have your routes setup), you should be able to render partials for objects.  i.e. I should be able to...</abstract>
  <text>The same way that link_to can infer the URL you want just by passing it objects (assuming you have your routes setup), you should be able to render partials for objects.  i.e. I should be able to define a _book.html.erb partial and then in a catalog page, make a call like &quot;render @book&quot; and it will render the right partial, passing it the object as a local.  It could even support arrays of objects and render them as collections.</text>
  <closed_at nil="true"></closed_at>
  <vote_count type="integer">2</vote_count>
  <comments_count type="integer">2</comments_count>
  <status nil="true"></status>
  <forum>
    <id type="integer">10012</id>
    <name>Rails</name>
    <key deprecated="true">rails3</key>
  </forum>
  <response nil="true"></response>
  <created_by>
    <supporter>
      <user>
        <id type="integer">221412</id>
        <display_name>nhorton</display_name>
        <name deprecated="true">nhorton</name>
        <username deprecated="true">nhorton</username>
      </user>
    </supporter>
  </created_by>
  <created_at type="datetime">2009-01-21T22:54:26Z</created_at>
  <updated_at type="datetime">2009-01-21T22:54:26Z</updated_at>
  <page deprecated="true">
    <key>rails3</key>
  </page>
</suggestion>
<suggestion>
  <id type="integer">110269</id>
  <url>http://rails.uservoice.com/pages/10012-rails/suggestions/110269-document-load-ordering</url>
  <title>Document load ordering</title>
  <abstract>Upgrading to Rails 2.2 has been a disaster for us because there were massive changes in load ordering and no documentation of it.  Could someone please document this critical issue?</abstract>
  <text>Upgrading to Rails 2.2 has been a disaster for us because there were massive changes in load ordering and no documentation of it.  Could someone please document this critical issue?</text>
  <closed_at nil="true"></closed_at>
  <vote_count type="integer">1</vote_count>
  <comments_count type="integer">0</comments_count>
  <status nil="true"></status>
  <forum>
    <id type="integer">10012</id>
    <name>Rails</name>
    <key deprecated="true">rails3</key>
  </forum>
  <response nil="true"></response>
  <created_by>
    <supporter>
      <user>
        <id type="integer">221412</id>
        <display_name>nhorton</display_name>
        <name deprecated="true">nhorton</name>
        <username deprecated="true">nhorton</username>
      </user>
    </supporter>
  </created_by>
  <created_at type="datetime">2009-01-27T02:27:27Z</created_at>
  <updated_at type="datetime">2009-01-27T02:27:27Z</updated_at>
  <page deprecated="true">
    <key>rails3</key>
  </page>
</suggestion>
  </supported_suggestions>
  <created_at type="datetime">2009-02-08T04:07:00Z</created_at>
  <updated_at type="datetime">2009-02-08T04:07:20Z</updated_at>
</user>
