commit 34ceb09fb63518cf86bd6187fafeb4a3df0eb85e parent baff321b2bc9979c02a7d0a02e6440c3ee2403be Author: Christian Grothoff <christian@grothoff.org> Date: Sat, 2 Sep 2017 15:25:54 +0200 keep track of issues observed looking at /pay some more Diffstat:
| A | TODO | | | 10 | ++++++++++ |
1 file changed, 10 insertions(+), 0 deletions(-)
diff --git a/TODO b/TODO @@ -0,0 +1,10 @@ +Major issues with /pay: + +1) Why is there a 'paid' field in merchant_contract_terms DB table? + +2) If we do have the row_id of merchant_contract_terms, why do we store + the full h_contract_terms/merchant_pub again and again in the other tables? + +3) What happens if we store in merchant_transactions some timestamp/exchange + and then the deposits (partially) fail? Do we undo the deposits? Do we + allow a 2nd round of /pay? What happens if the exchange differs the 2nd time?