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

Ruby Rails 5-保存回滚,因为嵌套模型父模型未在子模型之前保存,ruby,ruby-on-rails-5,nested-forms,nested-attributes,nested-form-for,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 thr

好了,伙计们,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 %>
###############################################################################
###用户模型
###############################################################################
类用户<应用程序记录
有一个:profile,与::user相反
接受\u嵌套的\u属性\u for:profile,允许\u destroy:true
终止
###############################################################################
###剖面模型
###############################################################################
类配置文件<应用程序记录
属于:用户,与::profile相反
验证用户是否存在
终止
###############################################################################
###用户控制器
###############################################################################
类UsersController
  • true,:值=>'2'> true,:值=>'1'> 帐户配置文件
    我遇到了类似的问题(没有使用嵌套属性保存)


    在控制器中,我将我的
    @user.build\u profile
    更改为
    @user.profile.build(params[:profile])
    ,它解决了这个问题。

    好的,我在另一个问题上重新表述了这个问题,最终找到了答案。所以我将我的答案粘贴在那里,以防有人以我在这里提问的方式搜索问题

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

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

  • 与之相反的是:
  • 自动保存:正确
  • 接受\u嵌套的\u属性\u for:model,允许\u destroy:true
  • 这是用户模型,然后我会解释

    class User < ApplicationRecord
      has_one :profile, inverse_of: :user, autosave: true
      accepts_nested_attributes_for :profile, allow_destroy: true
    end
    
    如果您查看它,它将从头开始重建配置文件,并将与您正在编辑的当前用户匹配的记录的用户id重置为null。所以要非常小心,因为我已经看到了大量的帖子在做这件事
    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)