Question

模型

class PushNotificationRequest < ApplicationRecord
  serialize :details

移民

class CreateNotificationRequests < ActiveRecord::Migration[5.2]
  def change
    create_table :notification_requests do |t|
      t.references :order, references: :spree_orders, index: false
      t.string :key                             
      t.json :details                           
      t.string :type
      t.timestamps
    end
  end
end

在控制台上创建数据

PushNotificationRequest.create(order: Spree::Order.last, details: {a: 2})

MySQL怪异存储

mysql> select * from notification_requests;
+----+----------+------+----------------+-------------------------+-----------+---------------------+---------------------+
| id | order_id | key  | details        | type                    | status    | created_at          | updated_at          |
+----+----------+------+----------------+-------------------------+-----------+---------------------+---------------------+
|  7 |       19 | NULL | "---\n:a: 2\n" | PushNotificationRequest | INITIATED | 2019-01-09 13:45:40 | 2019-01-09 13:45:40 |
+----+----------+------+----------------+-------------------------+-----------+---------------------+---------------------+

details列存储为一些奇怪的字符串，而不是正确的json 我正在使用mysql 8.0.12和rails 5.12

有什么我想念的吗？

Answer 1

在这种情况下，我认为您需要定义以将属性专门序列化为JSON：

class PushNotificationRequest < ApplicationRecord
  serialize :details, JSON

您确定MySQL能够顺便存储JSON吗？（我只对PostgreSQL有经验）

Answer 2

根据文档Keep in mind that database adapters handle certain serialization tasks for you. For instance: json and jsonb types in PostgreSQL will be converted between JSON object/array syntax and Ruby Hash or Array objects transparently. There is no need to use serialize in this case.

serialize :details不是必需的，并且以某种方式破坏了序列化。删除后，在mysql中获得了正确的json。

Rails 5.2应用程序记录的不正确的json序列化

2 个答案: