Я разрабатывал Pork.dbObject самостоятельно. (Простой PHP ORM и Активная Рекордная реализация) главная причина состоит в том, что я нахожу большинство ORMs слишком тяжелый.
основная мысль о Pork.dbObejct должна быть легка и проста настроить. Никакой набор XML-файлов, всего один вызов функции в конструкторе обязать его, и addRelation или addCustomRelation определять отношение к другому dbObject.
Посмотрели на него: Pork.dbObject
Why is it so important that you use an instance variable(variables who's names begin with '@', eg: @object) in your partial? It's not a good habit to get into. Using instance variables in partials complicates the control flow, which facilitates bugs and makes reuse of partials more difficult. This blog post explains the problem a little more in depth.
Really you have two options. The first option is the suggested solution.
Change all instance variables to a local variable and pass it to the partial with the locals argument of render.
Set the instance variable before the partial is rendered. Partials have access to all the instance variables that your controller sets.
Again instance variables in partials are bad. You should never set instance variables just because your partials are already written to use them. Rewrite the partial instead.
You could always do @profile = profile
in the partial.
это проще
<%= render :partial => "profiles/show", :collection => @profiles %>
на частичном _show.html.erb
<%= profile.fullname %>
надеюсь помогло