# ChangeSets and validations

Changesets define data transformations(type casting, filtering, validation)

```elixir
def changeset(%User{} = user, attrs) do
  user
  #mark new data(attrs) and columns to update
  |> cast(attrs, [:name, :email, :bio, :age]) 
  #ensure fields present
  |> validate_required([:name, :email, :bio])
  |> validate_length(:bio, min: 2)
  |> validate_format(:email, ~r/@/)
  |> validate_inclusion(:age, 18..100)
  |> unique_constraint(:email)

end
```

```elixir
changeset = Ecto.Changeset.cast(%User{}, %{"age" => "0"}, [:age])
user = Repo.insert!(changeset)
```

### Validations vs Constraints

Most validations(expect ones marked unsafe) don't require the db

Constraints rely on the db and are always safe

## Advanced

Conditionally validate\_required

```elixir
def changeset(chat_channel, attrs) do
  chat_channel
  |> cast(attrs, [:type, :user_id, :event_id, :subevent_id, :group_id])
  |> validate_required([:type])
  |> (fn cs ->
  case get_field(cs, :type) do
      "event" -> cs |> validate_required([:event_id])
      "group" -> cs |> validate_required([:subevent_id, :group_id])
      "user" -> cs |> validate_required([:user_id])
      _ -> cs
    end
    end).()
end
```

Can have multiple changes


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://openai.gitbook.io/code-cheatsheets/all/elixir/phoenix/db_ecto/changesets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.