【问题标题】:Rails4 Association autosave does not workRails4 关联自动保存不起作用
【发布时间】:2015-10-11 20:16:57
【问题描述】:

我是 Rails 的新手。

我有一个模型关联(belongs_to -> has_many),但应用程序没有将关联模型的 id 保存在外键列中。

迁移文件:

class CreatePartnerAdvertisements < ActiveRecord::Migration
  def change
    create_table :partner_advertisements do |t|
        t.belongs_to :user,     index: true
        t.belongs_to :county,   index: true

        t.text    :description, null: true

        t.string  :city,        null: true,     limit: 100

        t.integer :age,         null: false,    limit: 120
        t.integer :height,      null: true,     limit: 300
        t.integer :weight,      null: true,     limit: 300

        t.timestamps null: false

        t.timestamps null: false
    end
  end
end

保存后外键列始终为1的模型

class PartnerAdvertisement < ActiveRecord::Base
    belongs_to :user,   autosave: true
    belongs_to :county, autosave: true

    validates_associated  :county
end

这是风景

    <%= form_for(@partner_advertisement) do |f| %>


  <div class="field">
    <%= f.label :county %><br />
    <%= collection_select :partner_advertisement ,:county_id, County.all, :id, :name, {selected: @partner_advertisement.county_id} %>
  </div>

<% end %>

所以这里,我从列表中选择了一个县,但是当parter_advertisement保存时,county_id没有被修改...和user_id一样...

所以似乎在 Rails 中关联保存不起作用。当然,如果在控制器中我从请求中获得正确的参数,我可以手动保存外键 ID。

但对我来说,如果 ActiveRecord 可以自动保存 partner_advertisement 的外键,那就太好了。

控制器:

class PartnerAdvertisementsController < ApplicationController
  before_action :authenticate_user!
  before_action :set_partner_advertisement, only: [:show, :edit, :update, :destroy]

  # GET /partner_advertisements
  # GET /partner_advertisements.json
  def index
    @partner_advertisements = PartnerAdvertisement.where(is_active: true)
  end

  # GET /partner_advertisements/1
  # GET /partner_advertisements/1.json
  def show
  end

  # GET /partner_advertisements/new
  def new
    @partner_advertisement = PartnerAdvertisement.new
  end

  # GET /partner_advertisements/1/edit
  def edit
  end

  # POST /partner_advertisements
  # POST /partner_advertisements.json
  def create
    @partner_advertisement = PartnerAdvertisement.new(partner_advertisement_params)
    #@partner_advertisement.user_id = current_user.id

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

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

  # DELETE /partner_advertisements/1
  # DELETE /partner_advertisements/1.json
  def destroy
    @partner_advertisement.destroy
    respond_to do |format|
      format.html { redirect_to partner_advertisements_url, notice: 'Partner advertisement was successfully destroyed.' }
      format.json { head :no_content }
    end
  end

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

    # Never trust parameters from the scary internet, only allow the white list through.
    def partner_advertisement_params
      #params[:partner_advertisement]
      params.require(:partner_advertisement).permit(:age, :height, :weight, :city, :county, :description, :style, :club, :level, :goal, :weekly, :occasionally, :years, :is_active)
    end
end

更新请求的日志没有任何错误:

Started PATCH "/partner_advertisements/1" for 10.0.2.2 at 2015-10-11 20:01:06 +0000
Cannot render console from 10.0.2.2! Allowed networks: 127.0.0.1, ::1, 127.0.0.0/127.255.255.255
Processing by PartnerAdvertisementsController#update as HTML
  Parameters: {"utf8"=>"✓", "authenticity_token"=>"dVNIi2H59EuZFrlrE+1ujRzDauJdc4Kkox6TbWNzpGK1mOoyfk6U8s9B/+HzASofd7DLe8/kdn4UKKIPCepjog==", "partner_advertisement"=>{"description"=>"yeap yeapr", "city"=>"Eger", "county_id"=>"9", "age"=>"45", "height"=>"43", "weight"=>"435", "style"=>"asdfdsafdf", "club"=>"adsfdf", "level"=>"asdfdsf", "goal"=>"sdfdsf", "weekly"=>"4", "occasionally"=>"3", "years"=>"3", "is_active"=>"1"}, "commit"=>"Update Partner advertisement", "id"=>"1"}
  [1m[35mUser Load (1.6ms)[0m  SELECT  "users".* FROM "users" WHERE "users"."id" = ?  ORDER BY "users"."id" ASC LIMIT 1  [["id", 1]]
  [1m[36mPartnerAdvertisement Load (1.6ms)[0m  [1mSELECT  "partner_advertisements".* FROM "partner_advertisements" WHERE "partner_advertisements"."id" = ? LIMIT 1[0m  [["id", 1]]
Unpermitted parameter: county_id
  [1m[35m (0.1ms)[0m  begin transaction
  [1m[36m (0.2ms)[0m  [1mcommit transaction[0m
Redirected to http://localhost:3000/partner_advertisements/1
Completed 302 Found in 15ms (ActiveRecord: 3.6ms)

所以你可以看到请求中的county_id是9,但是在数据库中保存后总是1... :(

【问题讨论】:

  • 服务器日志中是否可能存在未经允许的参数错误?你也可以展示你的控制器吗?

标签: ruby-on-rails ruby-on-rails-4 activerecord associations


【解决方案1】:

您需要在您的partner_advertisement_params 中允许county_id

只需像这样添加它:

def partner_advertisement_params
  #params[:partner_advertisement]
  params.require(:partner_advertisement).permit(:age, :height, :weight, :city, :county, :description, :style, :club, :level, :goal, :weekly, :occasionally, :years, :is_active, :county_id)
end

【讨论】:

  • 是的,你是对的,但为什么我需要允许外键?因为我允许 :county...
  • 这是因为county_id 被定义为您的collection_select 的名称。这实际上很好,因为数据库字段也会有这个名称。 county_id 是到达控制器的参数的名称。 county 只是协会的名称。
猜你喜欢
  • 1970-01-01
  • 2020-12-05
  • 1970-01-01
  • 2022-11-09
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 2019-11-10
相关资源
最近更新 更多