Document plm migration #37
No reviewers
Labels
No labels
bug
dependencies
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: plume/documentation#37
Loading…
Reference in a new issue
No description provided.
Delete branch "plm-migration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@ -20,0 +37,4 @@New files will be generated in `migrations/postgres` and `migrations/sqlite`, called `up.sql` and `down.sql`.The former should run the actual migration, and the later undo it.You can also run some Rust code in migrations, by writing it in comments starting with `#!`, and wrapped in a closure takingactually it can in theory be the full path to a function too (not tested, but I will soon because the code for timeline migration will probably be to long for me to prefix it with --#! without getting annoyed)
@ -20,0 +37,4 @@New files will be generated in `migrations/postgres` and `migrations/sqlite`, called `up.sql` and `down.sql`.The former should run the actual migration, and the later undo it.You can also run some Rust code in migrations, by writing it in comments starting with `#!`, and wrapped in a closure takingOh, I didn't noticed that! Nice!
I added something, but I'm not sure about the exact syntax. 😬
@ -20,0 +37,4 @@New files will be generated in `migrations/postgres` and `migrations/sqlite`, called `up.sql` and `down.sql`.The former should run the actual migration, and the later undo it.You can also run some Rust code in migrations, by writing it in comments starting with `#!`, and wrapped in a closure takingyour syntax is what I expect it to be, but hey, it's untested so maybe it's a bit different? Who knows?
@ -20,0 +37,4 @@New files will be generated in `migrations/postgres` and `migrations/sqlite`, called `up.sql` and `down.sql`.The former should run the actual migration, and the later undo it.You can also run some Rust code in migrations, by writing it in comments starting with `#!`, and wrapped in a closure takingok I tested it, and it is basically what you wrote
--#! crate::migrations::functions::timeline_creationsource/update.html.mdandsource/environment.html.mdwere not updated, and line 73 ofsource/development.html.mdwas forgotten tooFor some reason they didn't appeared in the search result of my editor… 🤷♀️ Thank you.
Pull request closed