challenger

OAuth 2.0-based authentication service that validates user can receive messages at a certain address
Log | Files | Refs | Submodules | README | LICENSE

commit 3ea1ffbe5d367da55115cbcdc66b1b0786f84bff
parent 97f94a2f8f0ae2e34418890abbbdc8ebae56bcbe
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sat,  9 Mar 2024 21:02:46 +0100

improve drop.sql to avoid having to update it whenever new SQL revisions are added

Diffstat:
Msrc/challengerdb/drop.sql | 10++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/src/challengerdb/drop.sql b/src/challengerdb/drop.sql @@ -17,8 +17,14 @@ -- Everything in one big transaction BEGIN; --- Unregister patch (0001.sql) -SELECT _v.unregister_patch('challenger-0001'); +WITH xpatches AS ( + SELECT patch_name + FROM _v.patches + WHERE starts_with(patch_name,'challenger-') +) + SELECT _v.unregister_patch(xpatches.patch_name) + FROM xpatches; + DROP SCHEMA challenger CASCADE; -- And we're out of here...