View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009453 | Taler | merchant backend | public | 2025-01-11 11:04 | 2026-06-02 14:51 |
| Reporter | Christian Grothoff | Assigned To | Christian Grothoff | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | confirmed | Resolution | open | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | post-1.0 | ||||
| Summary | 0009453: enable data export [10d] | ||||
| Description | Given that it is clear that there will be merchants that host their business data at some operator, we need to implement some data export functionality that enables a merchant to export all business data from one instance and to re-import that business data at another instance. | ||||
| Tags | No tags attached. | ||||
| parent of | 0011457 | confirmed | Christian Grothoff | need API spec for data export/import [2d] |
| has duplicate | 0010491 | closed | Christian Grothoff | merchant backend should allow import/export/migration [meta] [14d] |
| Not all the children of this issue are yet resolved or closed. | ||||
|
|
I'm thinking that one way to do this *easily* might be to break up all tables that have an instance ID in them into new per-schema tables, so basically instead of everything in the 'merchant' schema, have 'merchant-$INSTANCE' schema. Populate that when an instance is being created, and then export / import the entire *schema* when migrating the instance. That would make it HARD to migrate if merchant backends use different versions (probably OK!), but otherwise radically simplify the migration logic itself (just dump/import the schema). We probably would keep the instance-table itself outside of the schema, as setting new credentials on the target backend is likely a good thing. Plus that way we can use that table to *discover* all the schema we expect. |
|
|
DB schema change is done, more much later... |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-01-11 11:04 | Christian Grothoff | New Issue | |
| 2025-01-11 11:04 | Christian Grothoff | Status | new => assigned |
| 2025-01-11 11:04 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2025-01-11 11:04 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2025-01-12 09:16 | Christian Grothoff | Status | assigned => confirmed |
| 2025-03-22 14:09 | Christian Grothoff | Category | mechant backend => merchant backend |
| 2026-02-07 23:00 | Christian Grothoff | Relationship added | child of 0010491 |
| 2026-04-27 00:44 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2026-04-27 00:44 | Christian Grothoff | Status | confirmed => assigned |
| 2026-04-27 00:44 | Christian Grothoff | Status | assigned => confirmed |
| 2026-04-27 22:38 | Christian Grothoff | Note Added: 0028481 | |
| 2026-05-09 00:11 | Christian Grothoff | Status | confirmed => assigned |
| 2026-05-09 00:38 | Christian Grothoff | Relationship deleted | child of 0010491 |
| 2026-05-09 00:38 | Christian Grothoff | Relationship added | has duplicate 0010491 |
| 2026-05-13 07:47 | Christian Grothoff | Summary | enable data export => enable data export [14d] |
| 2026-05-31 22:24 | Christian Grothoff | Relationship added | parent of 0011457 |
| 2026-06-02 14:51 | Christian Grothoff | Status | assigned => confirmed |
| 2026-06-02 14:51 | Christian Grothoff | Note Added: 0028754 | |
| 2026-06-02 14:51 | Christian Grothoff | Summary | enable data export [14d] => enable data export [10d] |
