类型不匹配插入:具有ecto更改集的binary_id [英] Type mismatch inserting :binary_id with Ecto changeset

查看:10
本文介绍了类型不匹配插入:具有ecto更改集的binary_id的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个表applications,其外键user_id是postgresuuid。我的web.ex中有:

  @primary_key {:id, :binary_id, autogenerate: true}
  @foreign_key_type :binary_id

我的型号是:

defmodule Dashboard.Application do
  use Dashboard.Web, :model

  alias Dashboard.User
  alias Dashboard.Path

  schema "applications" do
    field :name, :string
    belongs_to :user, User
    has_many :paths, Path
    timestamps
  end

  @required_fields ~w(name user_id)
  @optional_fields ~w()

  def changeset(model, params \ :empty) do
    model
    |> cast(params, @required_fields, @optional_fields)
  end
end

但是,当我尝试使用users表中的有效UUID对变更集执行插入操作时,会收到

[error] #PID<0.407.0> running Dashboard.Endpoint terminated
Server: localhost:4000 (http)
Request: POST /applications
** (exit) an exception was raised:
    ** (Ecto.ChangeError) value `<<184, 235, 134, 244, 95, 86, 74, 133, 159, 153, 31, 111, 16, 28, 76, 15>>` for `Dashboard.Application.user_id` in `insert` does not match type :binary_id
        (ecto) lib/ecto/query/planner.ex:33: anonymous fn/6 in Ecto.Query.Planner.fields/4
        (stdlib) lists.erl:1262: :lists.foldl/3
        (ecto) lib/ecto/query/planner.ex:21: Ecto.Query.Planner.fields/4
        (ecto) lib/ecto/repo/schema.ex:449: Ecto.Repo.Schema.dump_changes/5
        (ecto) lib/ecto/repo/schema.ex:77: anonymous fn/11 in Ecto.Repo.Schema.do_insert/4
        (ecto) lib/ecto/repo/schema.ex:477: anonymous fn/3 in Ecto.Repo.Schema.wrap_in_transaction/9
        (ecto) lib/ecto/pool.ex:292: Ecto.Pool.with_rollback/3
        (ecto) lib/ecto/adapters/sql.ex:582: Ecto.Adapters.SQL.transaction/8
        (ecto) lib/ecto/pool.ex:244: Ecto.Pool.outer_transaction/6
        (ecto) lib/ecto/adapters/sql.ex:551: Ecto.Adapters.SQL.transaction/3
        (dashboard) web/controllers/application_controller.ex:16: Dashboard.ApplicationController.create/2

检查user_id我看到:

pry(1)> params["user_id"] |> i
Term
  <<184, 235, 134, 244, 95, 86, 74, 133, 159, 153, 31, 111, 16, 28, 76, 15>>
Data type
  BitString
Byte size
  16
Description
  This is a binary: a collection of bytes. It's printed with the `<<>>`
  syntax (as opposed to double quotes) because it is not a
  UTF-8 encoded binary (the first invalid byte being `<<184>>`)
Reference modules
  :binary

这看起来像是试图向我插入有效的16字节UUID。我遗漏了什么?谢谢!

更新:以下是数据库架构:

              Table "public.applications"
   Column    |            Type             | Modifiers
-------------+-----------------------------+-----------
 id          | uuid                        | not null
 user_id     | uuid                        | not null
 name        | text                        | not null
 inserted_at | timestamp without time zone | not null
 updated_at  | timestamp without time zone | not null
Indexes:
    "applications_pkey" PRIMARY KEY, btree (id)
    "applications_user_id_index" btree (user_id)
Foreign-key constraints:
    "applications_user_id_fkey" FOREIGN KEY (user_id) REFERENCES users(id) ON DELETE CASCADE
Referenced by:
    TABLE "paths" CONSTRAINT "paths_application_id_fkey" FOREIGN KEY (application_id) REFERENCES applications(id) ON DELETE CASCADE

                 Table "public.users"
   Column    |            Type             | Modifiers
-------------+-----------------------------+-----------
 id          | uuid                        | not null
 email       | text                        | not null
 inserted_at | timestamp without time zone | not null
 updated_at  | timestamp without time zone | not null
 avatar      | text                        | not null
 name        | text                        | not null
 data        | jsonb                       | not null
Indexes:
    "users_pkey" PRIMARY KEY, btree (id)
    "users_email_index" UNIQUE, btree (email)
Referenced by:
    TABLE "applications" CONSTRAINT "applications_user_id_fkey" FOREIGN KEY (user_id) REFERENCES users(id) ON DELETE CASCADE
更新2: 我已升级到Phoenix 1.2和ecto 2.0.2,但问题仍然存在

更新3: 我想这可能是ECTO的一个漏洞。我已尽最大努力打开公关:https://github.com/elixir-ecto/ecto/pull/1585

推荐答案

使用binary_id的ecto架构要求数据是字符串格式的uuid,然后由ecto自动转换为16字节的二进制格式。

如果要直接使用二进制表示,可以将类型定义为:binary_id

schema "applications" do
  field :name, :string
  belongs_to :user, User, foreign_key: :user_id, type: :binary_id
  has_many :paths, Path
  timestamps
end

或者使用Ecto.UUID.load将二进制数据转换为字符串:

iex(38)> binary = Ecto.UUID.bingenerate()
<<91, 154, 58, 233, 38, 235, 76, 200, 188, 162, 112, 23, 233, 223, 191, 144>>
iex(39)> Ecto.UUID.load(binary)
{:ok, "5b9a3ae9-26eb-4cc8-bca2-7017e9dfbf90"} 

这篇关于类型不匹配插入:具有ecto更改集的binary_id的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆