b0180b0619
Thr reaason for this is that Ecto seems to be handling options differently when the custom type is used for a `belongs_to` field. For example if `belongs_to :thing, Thing, type: TypeID` is specified, the value for `type` will be `TypeIO`, which makes the opts valdiation fail. Using another name for `type`, makes it possible to both set `type` (The Ecto type of the field) and `column_type` (The column type in the database)`. |
||
|---|---|---|
| .github | ||
| lib | ||
| priv/spec | ||
| scripts | ||
| test | ||
| .formatter.exs | ||
| .gitignore | ||
| .tool-versions | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| mix.exs | ||
| mix.lock | ||
| README.md | ||
TypeID Elixir
A type-safe, K-sortable, globally unique identifier inspired by Stripe IDs
TypeIDs are a modern, type-safe, globally unique identifier based on the upcoming UUIDv7 standard. They provide a ton of nice properties that make them a great choice as the primary identifiers for your data in a database, APIs, and distributed systems. Read more about TypeIDs in their spec.
Installation
The package can be installed from hex by adding typeid_elixir to your list of dependencies in mix.exs:
def deps do
[
{:typeid_elixir, "~> 1.0"}
]
end
Spec
The original TypeID spec is defined here.
Usage with Ecto
TypeID implements the Ecto.ParameterizedType behaviour so you can use
TypeIDs as fields in your Ecto schemas.
defmodule MyApp.Accounts.User do
use Ecto.Schema
@primary_key {:id, TypeID, autogenerate: true, prefix: "acct", type: :uuid}
@foreign_key_type TypeID
# ...
end
Underlying types
TypeIDs can be stored as either :string or :uuid. :string will store
the entire TypeID including the prefix. :uuid stores only the UUID portion
and requires a :uuid or :uuid column.
Default type
The type used can be set globally in the application config.
config :typeid_elixir,
default_type: :uuid