Packages
literature
0.4.21
0.5.1
0.5.0
0.4.22
0.4.21
0.4.20
0.4.19
0.4.18
0.4.17
0.4.16
0.4.15
0.4.14
0.4.13
0.4.12
0.4.11
0.4.10
0.4.9
0.4.8
0.4.7
0.4.6
retired
0.4.5
0.4.4
0.4.3
0.4.2
0.4.1
0.4.0
0.3.6
0.3.5
0.3.4
0.3.3
0.3.2
0.3.1
0.3.0
0.2.18
0.2.17
0.2.16
0.2.15
0.2.14
0.2.13
0.2.12
0.2.11
0.2.10
0.2.9
0.2.8
0.2.7
0.2.6
0.2.5
0.2.4
0.2.3
0.2.2
0.2.1
0.2.0
0.1.32
0.1.30
0.1.29
0.1.28
0.1.27
0.1.26
0.1.25
0.1.24
0.1.23
0.1.22
0.1.21
0.1.20
0.1.19
0.1.18
0.1.17
0.1.16
0.1.15
0.1.14
0.1.13
0.1.12
0.1.11
0.1.10
0.1.9
0.1.8
0.1.7
0.1.6
0.1.5
0.1.4
0.1.3
0.1.2
0.1.1
0.1.0
A simple CMS / Blog
Current section
Files
Jump to
Current section
Files
lib/literature/migrations.ex
defmodule Literature.Migrations do
@moduledoc false
defdelegate up(opts \\ []), to: Literature.Migration
defdelegate down(opts \\ []), to: Literature.Migration
end
defmodule Literature.Migration do
@moduledoc """
Migrations create the database tables Literature needs.
## Usage
To use migrations in your application you'll need to generate an `Ecto.Migration` that wraps
calls to `Literature.Migrations`:
```bash
mix ecto.gen.migration add_literature
```
Open the generated migration in your editor and call the `up` and `down` functions on
`Literature.Migrations`:
```elixir
defmodule MyApp.Repo.Migrations.AddLiterature do
use Ecto.Migration
def up, do: Literature.Migrations.up(version: 1)
def down, do: Literature.Migrations.down(version: 1)
end
```
This will run the migrations for your database.
Now, run the migration to create the table:
```bash
mix ecto.migrate
```
"""
use Ecto.Migration
@callback up(Keyword.t()) :: :ok
@callback down(Keyword.t()) :: :ok
@callback migrated_version(Keyword.t()) :: non_neg_integer()
def up(opts \\ []) when is_list(opts) do
migrator().up(opts)
end
def down(opts \\ []) when is_list(opts) do
migrator().down(opts)
end
def migrated_version(opts \\ []) when is_list(opts) do
migrator().migrated_version(opts)
end
defp migrator do
Literature.Migrations.Postgres
end
end