@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.)
hq.recaptime.dev/wiki/Phorge
phorge
phabricator
Diviner: mention where database patches are stored
Summary:
I'm working on a new database patch and I've invested ~15 minutes in discovering
where these are stored, so to run these multiple times for testing purposes.
Test Plan:
Refresh the documentation:
./bin/diviner generate
Visit the page:
http://phorge.localhost/book/contrib/article/database/
Read the added info. Learn this new thing about the database table `meta_data.patch_status`.
Reviewers: O1 Blessed Committers, aklapper
Reviewed By: O1 Blessed Committers, aklapper
Subscribers: aklapper, tobiaswiese, Matthew, Cigaryno
Differential Revision: https://we.phorge.it/D26275
+16
+16
src/docs/contributor/database.diviner
+16
src/docs/contributor/database.diviner
···
204
204
205
205
**Test your patch**. Run `bin/storage upgrade` to test your patch.
206
206
207
+
Advanced Testing
208
+
================
209
+
210
+
If you are developing a database patch and you want to apply your patch more
211
+
than once, remember that the command `bin/storage upgrade` is smart enough not
212
+
to execute patches twice, but it does not allow a rollback, and it does
213
+
not allow to apply a specific patch by name anyway.
214
+
You may want to know that successfully applied patches are stored in this
215
+
database table:
216
+
217
+
{$NAMESPACE}_meta_data.patch_status
218
+
219
+
If you need to test a patch more than once, you can remove the line which lists
220
+
your patch from this database table, and test your patch again by running
221
+
`bin/storage upgrade`.
222
+
207
223
See Also
208
224
========
209
225