ELIXIR ECTO HOW TO
ELIXIR ECTO CODE

You need to start by running a similar migration that will create a new uuid column.

ELIXIR ECTO HOW TO

If you did not create the project yet, you could use a -binary-id flag to configure it automatically: mix phx.new your_app -binary-id How to migrate a table from integer to UUID primary key?Ĭhanging the primary key type in the table is not straightforward. If you’re starting a new project and would like all your schemas to leverage UUIDs for primary keys without customizing their migrations, you need to add the following line to your config file.Ĭonfig/config.exs config :your_app, yourapp. Insert query with returning option Using UUID as a default Let’s have a look at the resulting SQL query with and without returning: config: INSERT INTO 'users' ( 'email', 'inserted_at', 'updated_at' ) VALUES ( $ 1, $ 2, $ 3 ) ', ~ N, ~ N ]

ELIXIR ECTO CODE

It’s possible to ship code like: defmodule YourAppWeb. Properly scoping access to resources in web apps with non-trivial business logic is hard. Now I can use the enum in the Absinthe schema for permissions: defmodule CoolApp.Schema./orders/cc7a4c8b-1a90-4287-a983-3f6e10bd88d4/checkout

|> Dataloader.add_source(Permission, Permission.data()) # Define all enums specifically for 'The selected permission types'Įnum(:permissions_enum, values: _const()) I am defining the permissions enum for Absinthe there. In my “web” folder I have the schema.ex file. It can then be used in tables like (note the “add :name”): defmodule doĪdd :permission_id, references(:permissions, on_delete: :nothing)

So I named it in a way that always keeps it at the top of the list, 000_enums.exs defmodule do In my migrations (priv -> repo -> migrations) I created a migration that should be executed first. I also wanted to define the enums in the database. # Creates columns for inserted_at and updated_at timestamps.ĭ(Repo, query: &query/2) It is different than is required in Absinthe.Īnd using it, the Ecto schema looks like this (note the “name” field): defmodule do This is the Ecto syntax for defining enums. In the “api” folder, I create another file called ecto_enums.ex # Define all enums specifically for Ecto. Any other enums would be handled the same way and in the same file by creating more macros. This simply creates a macro that returns the enum. The Enum provides a location for all enum related macros.ĭefmacro permissions_const, do: _CALLER_) In the “api” folder, I created a file called enums.ex defmodule CoolApp.Enums ''' This allows me to “use” the enums within a module simply by referencing Enums Macros The Enums constants are where all enum values should be defined. A file called enums.ex holds the enum values. This folder holds all my constants throughout the app. I created a “constants” folder within the “api” folder. I wanted to be able to define my enums in a single location. The “backend” Ecto code in an “api” folder and the “frontend” Absinthe code in a “web” folder. I keep my code separated into two main folders in my lib folder in the project. If someone has an elegant solution that also solves this, I would really love to hear/see it. I really am loving it! I came up with a solution to my issue and wanted to share it. Now, it should be noted that I am new to Elixir. This would allow the frontend to query GraphQL directly for types and derivation of enums, ultimately allowing me to define the enums in one place only and eliminate the need to maintain them in multiple locations. These same enums needed to be referenced in Absinthe when creating GraphQL responses for a frontend. I wanted to create some enums that could be built into a Postgres DB and also referenced through Ecto.

Elixir ecto