ash-project/ash_postgres
1
0
Fork 0
mirror of https://github.com/ash-project/ash_postgres.git synced 2024-09-20 05:23:18 +12:00
Code Issues Projects Releases Packages Wiki Activity

docs: align ash.codegen params with current version (#246)

Browse source
This commit is contained in:
Albin Kocheril Chacko 2024-04-24 18:26:56 +05:30 committed by GitHub
parent d44c057345
commit 731a9faad3
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
documentation/tutorials/get-started-with-postgres.md
View file

@ -190,7 +190,7 @@ First, we'll create the database with `mix ash.setup`.
Then we will generate database migrations. This is one of the many ways that AshPostgres can save time and reduce complexity.
```bash
mix ash.codegen --name add_tickets_and_representatives
mix ash.codegen add_tickets_and_representatives
```
If you are unfamiliar with database migrations, it is a good idea to get a rough idea of what they are and how they work. See the links at the bottom of this guide for more. A rough overview of how migrations work is that each time you need to make changes to your database, they are saved as small, reproducible scripts that can be applied in order. This is necessary both for clean deploys as well as working with multiple developers making changes to the structure of a single database.