简体   繁体   English

Rails 5 DB迁移错误

[英]Rails 5 DB Migration error

I am trying to deploy my rails app to production but I am getting an error when trying to call rake db:migrate the error I get is ActiveRecord::StatementInvalid: Mysql2::Error: Illegal parameter data type bigint for operation 'get_lock': SELECT GET_LOCK(2398406209365187035, 0) I cannot see which migration is causing this and none of my migrations have the :limit set to convert to bigint from integer 我正在尝试将我的rails应用程序部署到生产中,但是在尝试调用rake db:migrate时遇到错误rake db:migrate我得到的错误是ActiveRecord::StatementInvalid: Mysql2::Error: Illegal parameter data type bigint for operation 'get_lock': SELECT GET_LOCK(2398406209365187035, 0)我看不到哪个迁移导致了这个,我的迁移都没有:limit设置为从integer转换为bigint

This deployed fine in staging so I am not sure where the issue lies. 这部署在舞台上很好,所以我不确定问题出在哪里。

My migrations are as follows: 我的迁移如下:

class CreateDatabase < ActiveRecord::Migration
  def change
    create_table "vuln_sets", id: :integer, force: :cascade, options: "ENGINE=InnoDB DEFAULT CHARSET=latin1" do |t|
      t.string "vulntype", null: false
      t.string "displayname", null: false
      t.string "bulletinfamily", null: false
      t.integer "vulncount", default: 0, null: false
      t.boolean "active", default: false, null: false
      t.timestamp "timestamp", default: -> { "CURRENT_TIMESTAMP" }, null: false
      t.index ["vulntype"], name: "vulntypeindex", unique: true
    end
  end
end

Second migration: 第二次迁移:

class DeviseCreateUsers < ActiveRecord::Migration[5.0]
  def change
    create_table :users do |t|
      ## Database authenticatable
      t.string :email,              null: false, default: ""
      t.string :encrypted_password, null: false, default: ""

      ## Recoverable
      t.string   :reset_password_token
      t.datetime :reset_password_sent_at

      ## Rememberable
      t.datetime :remember_created_at

      ## Trackable
      t.integer  :sign_in_count, default: 0, null: false
      t.datetime :current_sign_in_at
      t.datetime :last_sign_in_at
      t.string   :current_sign_in_ip
      t.string   :last_sign_in_ip

      ## Confirmable
      # t.string   :confirmation_token
      # t.datetime :confirmed_at
      # t.datetime :confirmation_sent_at
      # t.string   :unconfirmed_email # Only if using reconfirmable

      ## Lockable
      # t.integer  :failed_attempts, default: 0, null: false # Only if lock strategy is :failed_attempts
      # t.string   :unlock_token # Only if unlock strategy is :email or :both
      # t.datetime :locked_at


      t.timestamps null: false
    end

    add_index :users, :email,                unique: true
    add_index :users, :reset_password_token, unique: true
    # add_index :users, :confirmation_token,   unique: true
    # add_index :users, :unlock_token,         unique: true
  end
end

I've ran into this issue today. 我今天遇到过这个问题。 Seems like MySQL/MariaDB implementation of get_lock has changed: 似乎MySQL / MariaDB的get_lock实现已经改变:

On MariaDB 10.2: 在MariaDB 10.2上:

> select get_lock(1234567890, 0);
+-------------------------+
| get_lock(1234567890, 0) |
+-------------------------+
|                       1 |
+-------------------------+

On MariaDB 10.3: 在MariaDB 10.3上:

> select get_lock(1234567890, 0);
ERROR 4079 (HY000) at line 1: Illegal parameter data type bigint for operation 'get_lock'

Upgrade Rails to 5.1.6. 将Rails升级到5.1.6。

Issue fixed by: https://github.com/rails/rails/pull/31521 问题修复: https//github.com/rails/rails/pull/31521

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM