aboutsummaryrefslogtreecommitdiff
path: root/src/exchangedb
AgeCommit message (Collapse)Author
2023-09-10major exchange DB schema change: store common properties of batch deposit in ↵Christian Grothoff
batch_deposits table, and coin-specific ones in coin_deposits table; plus minor cleanups
2023-09-06remove locking, we'll revert to sequential use as locking requires superuserChristian Grothoff
2023-09-01-spellingChristian Grothoff
2023-08-31reserve space for wallet_data_hash in schemaChristian Grothoff
2023-08-27-fix issue with multiple dbinit running concurrentlyChristian Grothoff
2023-08-23add anastasis facade to fakebankChristian Grothoff
2023-08-01amount-specific functions, not proceduresÖzgür Kesim
2023-07-30add missing prepared statementsChristian Grothoff
2023-07-30remove wrap_size, obsoleteChristian Grothoff
2023-07-30remove pre-array batch reserves-in insertion logicChristian Grothoff
2023-07-30misc bug fixes in batch insertChristian Grothoff
2023-07-30unify to TEXT instead of mixing TEXT and VARCHARChristian Grothoff
2023-07-30-remove silly commentChristian Grothoff
2023-07-30-remove _tuple suffixChristian Grothoff
2023-07-30-fix typosÖzgür Kesim
2023-07-30[pq] use GNUNET_PQ_get_oid_by_name consistentlyÖzgür Kesim
2023-07-29dceChristian Grothoff
2023-07-29migration to new amount style for exchangedbChristian Grothoff
2023-07-28taler_amount type introduced in reserves table and corresponding functionsÖzgür Kesim
- current_balance is now a taler_amount - all C-functions, SQL-statements and stored procedures adjusted accordingly. => make check passes all tests in testing.
2023-07-28FAILING attempt to make echange.reserve use taler_amountÖzgür Kesim
Fails with > TALER_PREFIX=/usr/local ./test-exchangedb-postgres 2023-07-28T19:02:25.150845+0200 /home/oec/projects/taler/exchange/src/exchangedb/.libs/test-exchangedb-postgres-2559159 WARNING Could not run PSQL on file /usr/local/share/taler//sql/exchange/drop.sql: psql exit code was 3 2023-07-28T19:02:32.488085+0200 pq-2559159 ERROR Query `call_withdraw' failed with result: invalid input syntax for type bigint: "(1,1000)"/(null)/ERROR: invalid input syntax for type bigint: "(1,1000)" CONTEXT: PL/pgSQL function exchange_do_withdraw(bytea,taler_amount,bytea,bytea,bytea,bytea,bytea,bigint,bigint,boolean) line 23 at SQL statement /PGRES_FATAL_ERROR/ERROR: invalid input syntax for type bigint: "(1,1000)" CONTEXT: PL/pgSQL function exchange_do_withdraw(bytea,taler_amount,bytea,bytea,bytea,bytea,bytea,bigint,bigint,boolean) line 23 at SQL statement 2023-07-28T19:02:32.488146+0200 /home/oec/projects/taler/exchange/src/exchangedb/.libs/test-exchangedb-postgres-2559159 ERROR Assertion failed at test_exchangedb.c:1428.
2023-07-28[pq] added helper to load oids of composite typesÖzgür Kesim
- TALER_PQ_load_oids_for_composite_types added - Called during postgres-initialization
2023-07-28finalize v3/v4 -> v2 exchange schema mergerÖzgür Kesim
2023-07-28finalize v3/v4 -> v2 exchange schema mergerÖzgür Kesim
2023-07-28combine v3 and v4 of exchange schema into v2 due to major incompatible tuple ↵Christian Grothoff
change forthcoming
2023-07-28-fix type defsChristian Grothoff
2023-07-27[WiP] added TALER_AMOUNT type to Postgres - first in age_withdrawÖzgür Kesim
- Added a type TALER_AMOUNT (val INT8, frac INT4) to Postgres. - Added PLSQL functions/procedures - amount_normalize(a) - amount_add(a, b) - amount_left_minus_right(l, r, diff, ok bool) - Added PQ-helper functions - TALER_PQ_query_param_amount_tuple() - TALER_PQ_result_spec_amount_tuple() - In table 'age_withdraw', changed fields 'amount_with_fee_val' and '..._frac' into single field 'amount_with_fee' be of type TALER_AMOUNT - Changed functions/stored procedures 'do_age_withdraw' and 'get_age_withdraw' to use new APIs. => make check runs through without errors, age-withdraw and -reveal test passes.
2023-07-26[age-withdraw] WIP - database transaction during reveal works nowÖzgür Kesim
The test for age-restriction still fail, but the database transactions, including passing arrays in/out the PQ-helpers works.
2023-07-24[age-withdraw] first tests passÖzgür Kesim
age-withdraw successfully tested (no reveal yet): 1. reserve filled with amount large enough to trigger kyc 2. kyc oauth2 test daemon sets birthday to 2015-00-00 3. usual withdraw fails with CONFLICT and AGE_RESTRICTION_REQUIRED 4. age-withdraw with loo large of an maximum age fails 5. age-withdraw with appropriate maximum age succeeds
2023-07-23kyc logic with birthdate setting test addedÖzgür Kesim
1. Added age-requirement check in withdraw-handler (like in batch-withdraw) 2. In test_exchange_api_age_restriction: - kyc-oauth2 started, with static birthdate in answers - withdraw triggers kyc - second withdraw fails due to age restriction requirements
2023-07-23[kyc] put reserve_pub into legitimization_requirementsÖzgür Kesim
2023-07-23Added reserve_pub to kyc legitimization_processesÖzgür Kesim
Where applicable, the reserve_pub will be passed on to the kcy-legitimization process and persisted along with h_payto. This allows us to set a birthday on the reserve itself, once a related kyc-process has provided one.
2023-07-16fix taler-aggregator-benchmarkChristian Grothoff
2023-06-27-fix parameter in stored proceduresÖzgür Kesim
2023-06-26-fixed typosÖzgür Kesim
2023-06-26add exchange_do_age_withdraw.sqlÖzgür Kesim
2023-06-26-ruuid not neededÖzgür Kesim
2023-06-26Merge branch 'master' into age-withdraw-mergeÖzgür Kesim
2023-06-26[age-withdraw] age-withdraw commit- and reveal-handlers implemented, 12/nÖzgür Kesim
The handlers for the commit- and reveal-phases of the age-withdraw HTTP-endpoints are implemented, yet not active. Still missing: - support for age-withdraw is missing in lib/. - tests
2023-06-25fix testChristian Grothoff
2023-06-25-fix typoChristian Grothoff
2023-06-23fix #7870Christian Grothoff
2023-06-05Merge branch 'master' into age-withdrawÖzgür Kesim
2023-06-04code cleanup, fixing misc. memory leaks in the processChristian Grothoff
2023-06-03-loggingChristian Grothoff
2023-06-03add DB idempotency testChristian Grothoff
2023-06-03Merge branch 'master' into age-withdrawÖzgür Kesim
2023-06-02make CREATE TYPE usage idempotentFlorian Dold
PostgresSQL doesn't have a CREATE TYPE OR REPLACE, so we have to work around this with exception handling.
2023-05-21-fix SQLChristian Grothoff
2023-05-21-typoChristian Grothoff
2023-05-18array-based do_reserves_in_insertChristian Grothoff