kwando
Custom Ecto.Type for :id is not "loaded"
I have a custom ecto type defined like below.
defmodule MyApp.Account do
use Ecto.Schema
@primary_key {:id, MyApp.AccountID, autogenerate: true}
schema "accounts" do
field :name, :string
# ... more fields here
end
end
defmodule MyApp.AccountID do
@behaviour Ecto.Type
@hashids Hashids.new(min_len: 8, salt: "**salt**")
@moduledoc """
Converts integers to Hashids.
See http://hashids.org/ for more information.
"""
def type(), do: :id
def cast(term) when is_integer(term), do: {:ok, Hashids.encode(@hashids, term)}
def cast(term) when is_binary(term), do: dump(term)
def cast(_), do: :error
def dump(term) when is_binary(term) do
Hashids.decode!(@hashids, term)
|> case do
[int] -> {:ok, int}
_ -> :error
end
end
def dump(term) when is_integer(term), do: {:ok, term}
def dump(_), do: :error
def load(term) when is_integer(term), do: cast(term)
def load(_), do: :error
end
When inserting into a Repo I get integer (:id) keys back from Ecto.
%MyApp.Account{name: "hello"}
|> MyApp.Repo.insert
This returns {:ok, %MyApp.Account{id: 323, name: "hello"} but I’m expecting that the id field should be passed through the load function on my custom type on it’s way back from the database.
Is this a bug in Ecto or am I doing something wrong?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Practical resources that improve the lives of professional developers.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #elixirconf-us
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #performance
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Develop your skills with books, videos, and courses.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 10 of 10 Posts!
kwando
I’m using the name
:idbecause I want my database to generate the primary key for me, I have not figured out another way to “trick” the database (postgres) do it for me.idi527
Your code seems to work for me
It returns user id as integer from
insertsince it returns what it sends, and it sends an integer.kwando
Yep, it works fine when using
Repo.get/2. But see whatRepo.insert(%Users{name: "hello"})returnsidi527
See Response of insert doesn't contain default values - #3 by aseigo
kwando
Yes, but in this case I’m actually getting the auto incremented integer from the database..
idi527
You are right, I’m not thinking straight …
kwando
Hmm, if I swap
autogenerate: trueforread_after_writes: trueon the field options it seems to work as expectedCan someone verify if this is the correct thing to do?
michalmuskala
This might be a bug in ecto that we don’t correctly load ids. Could you open an issue, ideally with a simple way to reproduce the issue?
kwando
I’ll build you something to play with tomorrow
obsidienne
I can’t find any issue on github. Can you post here the issue number ?
thanks