View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004912 | Taler | merchant backend | public | 2017-02-22 16:03 | 2017-06-06 12:18 |
| Reporter | Marcello Stanisci | Assigned To | Marcello Stanisci | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.3 | Fixed in Version | 0.3 | ||
| Summary | 0004912: order_id's role in tracking activity | ||||
| Description | order_id needs to be placed "somewhere" in the db, so that for the MFE is easy to query it and get results. Right now, order_id is NOT in the merchant_transactions table, so the /history handler should (?) do some more db queries in order to return meaningful results. Figure out what is the best place to put order_id.. | ||||
| Tags | No tags attached. | ||||
| we keep two tables: one that maps order_id to proposal data and relative timestamp, and one that maps proposal data hashes to payment details. So in case of /history we retrieve order ids and proposal data from the first table, then hash proposal data and get other relevant details from the second table. The reason to split those two tables is that the first one offers a view more frontend-friendly: we keep there only data understood by frontends. OTOH, the second one offers a view which is closer to what a merchant backend and an exchange are interested in in terms of payments. | |
| From 2fafeda, order_id now belongs to 'merchant_proposal_data' table. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-02-22 16:03 | Marcello Stanisci | New Issue | |
| 2017-02-22 16:03 | Marcello Stanisci | Status | new => assigned |
| 2017-02-22 16:03 | Marcello Stanisci | Assigned To | => Marcello Stanisci |
| 2017-02-23 17:13 | Marcello Stanisci | Note Added: 0011841 | |
| 2017-02-23 20:20 | Marcello Stanisci | Status | assigned => informing |
| 2017-02-23 20:20 | Marcello Stanisci | Resolution | open => fixed |
| 2017-02-23 20:20 | Marcello Stanisci | Note Added: 0011842 | |
| 2017-04-01 22:47 | Christian Grothoff | Product Version | => git (master) |
| 2017-04-01 22:47 | Christian Grothoff | Fixed in Version | => 0.3 |
| 2017-04-01 22:47 | Christian Grothoff | Target Version | => 0.3 |
| 2017-06-06 12:18 | Christian Grothoff | Status | informing => closed |
| 2025-03-22 13:09 | Christian Grothoff | Category | mechant backend => merchant backend |