Rails 5 - 保存回滚,因为在子模型之前没有保存嵌套模型父模型

时间:2017-03-10 00:49:37

标签: ruby ruby-on-rails-5 nested-forms nested-attributes nested-form-for

好的人,Rails 5确实有其不同于Rails 4的细微差别。我发现的是每次我点击表单上的提交按钮时都会重新加载错误个人资料用户必须存在个人资料用户不能为空。表单加载正常,包括嵌套的模型表单,但出于任何原因,在尝试使用以下输出将子模型保存到控制台之前未能保存父模型:

Puma starting in single mode...
* Version 3.7.0 (ruby 2.2.6-p396), codename: Snowy Sagebrush
* Min threads: 5, max threads: 5
* Environment: development
* Listening on tcp://0.0.0.0:3000
Use Ctrl-C to stop
Started POST "/users" for 192.168.0.31 at 2017-03-09 18:51:04 -0500
Cannot render console from 192.168.0.31! Allowed networks: 127.0.0.1, ::1, 127.0.0.0/127.255.255.255
  ActiveRecord::SchemaMigration Load (0.2ms)  SELECT `schema_migrations`.* FROM `schema_migrations`
Processing by UsersController#create as HTML
  Parameters: {"utf8"=>"✓", "authenticity_token"=>"JPKO+ppAYqwWS8tWeXhEtbUWynXREu9jYlF0KIlyPgUaabHSzjPZocSxCvr/WEm1r6wAQyT1CvA6hNkZWfPD3Q==", "user"=>{"username"=>"test", "password"=>"[FILTERED]", "user_type_id"=>"1", "profile_attributes"=>{"first_name"=>"123", "middle_name"=>"123", "last_name"=>"123", "email"=>"123@123.com", "phone_number"=>"1234567890", "cell_number"=>"1234567890"}}, "commit"=>"Create User"}
   (0.1ms)  BEGIN
   (0.2ms)  ROLLBACK
  Rendering users/new.html.erb within layouts/application
  Rendered users/_form.html.erb (112.5ms)
  Rendered users/new.html.erb within layouts/application (118.7ms)
Completed 200 OK in 834ms (Views: 780.1ms | ActiveRecord: 2.2ms)

我在这种关系中遇到了其他问题,我想也许我需要重建项目。 以下是围绕此问题的所有相关代码:

###############################################################################
### Users Model
###############################################################################
    class User < ApplicationRecord
      has_one :profile, inverse_of: :user
      accepts_nested_attributes_for :profile, allow_destroy: true
    end

###############################################################################
### Profile Model
###############################################################################
    class Profile < ApplicationRecord
      belongs_to :user, inverse_of: :profile
      validates_presence_of :user
    end
###############################################################################
### Users Controller
###############################################################################
    class UsersController < ApplicationController
      before_action :set_user, only: [:show, :edit, :update, :destroy]

      # GET /users
      # GET /users.json
      def index
        @users = User.all
      end

      # GET /users/1
      # GET /users/1.json
      def show
        @user.build_profile
      end

      # GET /users/new
      def new
        @user = User.new
        @user.build_profile
      end

      # GET /users/1/edit
      def edit
        @user.build_profile
      end

      # POST /users
      # POST /users.json
      def create
        @user = User.new(user_params)

        respond_to do |format|
          if @user.save
            format.html { redirect_to @user, notice: 'User was successfully created.' }
            format.json { render :show, status: :created, location: @user }
          else
            format.html { render :new }
            format.json { render json: @user.errors, status: :unprocessable_entity }
          end
        end
      end

      # PATCH/PUT /users/1
      # PATCH/PUT /users/1.json
      def update
        respond_to do |format|
          if @user.update(user_params)
            format.html { redirect_to @user, notice: 'User was successfully updated.' }
            format.json { render :show, status: :ok, location: @user }
          else
            format.html { render :edit }
            format.json { render json: @user.errors, status: :unprocessable_entity }
          end
        end
      end

      # DELETE /users/1
      # DELETE /users/1.json
      def destroy
        @user.destroy
        respond_to do |format|
          format.html { redirect_to users_url, notice: 'User was successfully destroyed.' }
          format.json { head :no_content }
        end
      end

      private
        # Use callbacks to share common setup or constraints between actions.
        def set_user
          @user = User.find(params[:id])
        end

        # Never trust parameters from the scary internet, only allow the white list through.
        def user_params
          params.require(:user).permit(:username, :password, :user_type_id, profile_attributes: [:id, :user_id, :first_name, :middle_name, :last_name, :phone_number, :cell_number, :email])
        end
    end

###############################################################################
### Form View
###############################################################################
    <%= form_for(@user) do |f| %>
      <% if user.errors.any? %>
        <div id="error_explanation">
          <h2><%= pluralize(user.errors.count, "error") %> prohibited this user from being saved:</h2>

          <ul>
          <% user.errors.full_messages.each do |message| %>
            <li><%= message %></li>
          <% end %>
            <!--<li><%= debug f %></li>-->
          </ul>
        </div>
      <% end %>

      <div class="field">
        <%= f.label :username %>
        <%= f.text_field :username %>
      </div>

      <div class="field">
        <%= f.label :password %>
        <%= f.text_field :password %>
      </div>

      <div class="field">
        <% if params[:trainer] == "true" %>
          <%= f.label :user_type_id %>
          <%= f.text_field :user_type_id, :readonly => true, :value => '2' %>
        <% else %>
          <%= f.label :user_type_id %>
          <%= f.text_field :user_type_id, :readonly => true, :value => '1'  %>
        <% end %>
      </div>
        <h2>Account Profile</h2>
        <%= f.fields_for :profile do |profile| %>
          <%#= profile.inspect %>
            <div>
              <%= profile.label :first_name %>
              <%= profile.text_field :first_name %>
            </div>
            <div>
              <%= profile.label :middle_name %>
              <%= profile.text_field :middle_name %>
            </div>
            <div>
              <%= profile.label :last_name %>
              <%= profile.text_field :last_name %>
            </div>
            <div>
              <%= profile.label :email %>
              <%= profile.text_field :email %>
            </div>
            <div>
              <%= profile.label :phone_number %>
              <%= profile.telephone_field :phone_number %>
            </div>
            <div>
              <%= profile.label :cell_phone %>
              <%= profile.telephone_field :cell_number %>
            </div>
        <% end %>
      <div class="actions">
        <%= f.submit %>
      </div>
        <%= debug params %>
        <%= debug user %>
        <%= debug user.profile %>
    <% end %>

2 个答案:

答案 0 :(得分:4)

好吧,我在另一个问题上重述了这个问题,我终于找到了答案。所以我从那里粘贴我的答案,以防有人以与我在这里提问的方式相同的方式搜索问题。

好的,我正在回答我自己的问题,因为我知道很多人都在努力解决这个问题,而且我实际上有答案,而不是对文档做出模糊回应。

首先,我们将在这个例子中使用一对一的关系。创建关系时,需要确保父模型具有以下

  1. inverse_of:
  2. autosave:true
  3. accepts_nested_attributes_for:model,allow_destroy:true
  4. 以下是用户模型,然后我会解释,

    class User < ApplicationRecord
      has_one :profile, inverse_of: :user, autosave: true
      accepts_nested_attributes_for :profile, allow_destroy: true
    end
    

    在Rails 5中你需要inverse_of:因为这告诉Rails通过外键存在关系,并且在保存表单数据时需要在嵌套模型上设置它。现在,如果您要从关系线中离开自动保存:真实,那么您将使用 user_id 而不保存到配置文件表,只保留其他列,除非您有验证关闭然后它不会出错它只会在没有 user_id 的情况下保存它。这里发生的是 autosave:true 确保首先保存用户记录,以便 user_id 存储在的嵌套属性中个人资料模型。 简而言之,为什么 user_id 没有遍历到孩子并且它正在回滚而不是提交。 还有一个最后的问题是,有一些帖子在你的控制器中告诉你编辑路线你应该像我在我的帖子中添加 @ user.build_profile 。在评估控制台输出后,不要做它们是错误的结果

    Started GET "/users/1/edit" for 192.168.0.31 at 2017-03-12 22:38:17 -0400
    Cannot render console from 192.168.0.31! Allowed networks: 127.0.0.1, ::1, 127.0.0.0/127.255.255.255
    Processing by UsersController#edit as HTML
      Parameters: {"id"=>"1"}
      User Load (0.4ms)  SELECT  `users`.* FROM `users` WHERE `users`.`id` = 1 LIMIT 1
      Profile Load (0.5ms)  SELECT  `profiles`.* FROM `profiles` WHERE `profiles`.`user_id` = 1 LIMIT 1
       (0.1ms)  BEGIN
      SQL (0.5ms)  UPDATE `profiles` SET `user_id` = NULL, `updated_at` = '2017-03-13 02:38:17' WHERE `profiles`.`id` = 1
       (59.5ms)  COMMIT
      Rendering users/edit.html.erb within layouts/application
      Rendered users/_form.html.erb (44.8ms)
      Rendered users/edit.html.erb within layouts/application (50.2ms)
    Completed 200 OK in 174ms (Views: 98.6ms | ActiveRecord: 61.1ms)
    

    如果您看起来正在从头开始重建配置文件,并将user_id重置为null,以便与您正在编辑的当前用户匹配。所以要非常小心,因为我看到很多帖子提出了这个建议,并且花了我很多时间研究才找到解决方案!

答案 1 :(得分:0)

我遇到了类似的问题(没有使用嵌套属性保存)。

在控制器中,我将@user.build_profile更改为@user.profile.build(params[:profile])并解决了问题。