[taler-exchange] 05/06: use new 'was_decided' field instead of expensive subquery

[gnunet]

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository exchange.

commit 0c8b264dc840f22b9dc1d85b3556fc4b35d00bf7
Author: Christian Grothoff <grothoff@gnunet.org>
AuthorDate: Tue Oct 17 12:18:37 2023 +0200

    use new 'was_decided' field instead of expensive subquery
---
 src/exchangedb/exchange_do_expire_purse.sql | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/src/exchangedb/exchange_do_expire_purse.sql 
b/src/exchangedb/exchange_do_expire_purse.sql
index 2d9f7e09..1a17869a 100644
--- a/src/exchangedb/exchange_do_expire_purse.sql
+++ b/src/exchangedb/exchange_do_expire_purse.sql
@@ -35,12 +35,11 @@ SELECT purse_pub
       ,in_reserve_quota
   INTO my_purse_pub
       ,my_in_reserve_quota
-  FROM exchange.purse_requests
+  FROM purse_requests
  WHERE (purse_expiration >= in_start_time) AND
        (purse_expiration < in_end_time) AND
-   purse_pub NOT IN (SELECT purse_pub
-                       FROM purse_decision)
- ORDER BY purse_expiration ASC
+       NOT was_decided
+  ORDER BY purse_expiration ASC
  LIMIT 1;
 out_found = FOUND;
 IF NOT FOUND

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.