View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004484 | Taler | exchange | public | 2016-05-02 13:26 | 2016-05-03 10:37 |
| Reporter | Florian Dold | Assigned To | Christian Grothoff | 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 | feature | Reproducibility | N/A |
| Status | closed | Resolution | won't fix | ||
| Product Version | 0.0 | ||||
| Target Version | 0.0 | Fixed in Version | 0.0 | ||
| Summary | 0004484: taler-exchange-dbinit does not check if schema is correct | ||||
| Description | After running taler-exchange-dbinit, the exchange should run without any database access or schema problems. Right now if the schema is out of date, only running the exchange will surface that problem. | ||||
| Tags | No tags attached. | ||||
| I'm not sure there is a generic perfect solution here. Basically, what you're asking for is to introduce schema versioning and migration. But even that can always be buggy. For now, given that we're not in production, it doesn't even make sense to bother with writing schema upgrade logic. So what exactly do you propose the change to be here? | |
| On second thought, what I'm proposing doesn't make much sense in the context of dbinit. I just wanted a way to make sure that the database tables have the right schema *without* having to run actual HTTP requests that touch the database. But that's not easily possible I guess ... In the future we'd probably have some tool to check the database consistency which will also complain about a wrong schema, but for now we'll have to live with the exchange choking on a bad schema only after somebody made a request. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-05-02 13:26 | Florian Dold | New Issue | |
| 2016-05-02 13:26 | Florian Dold | Status | new => assigned |
| 2016-05-02 13:26 | Florian Dold | Assigned To | => Christian Grothoff |
| 2016-05-03 03:48 | Christian Grothoff | Note Added: 0010610 | |
| 2016-05-03 03:48 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2016-05-03 03:48 | Christian Grothoff | Status | assigned => feedback |
| 2016-05-03 03:48 | Christian Grothoff | Product Version | => 0.0 |
| 2016-05-03 03:48 | Christian Grothoff | Severity | minor => feature |
| 2016-05-03 09:28 | Florian Dold | Note Added: 0010617 | |
| 2016-05-03 09:28 | Florian Dold | Status | feedback => new |
| 2016-05-03 10:37 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2016-05-03 10:37 | Christian Grothoff | Reproducibility | have not tried => N/A |
| 2016-05-03 10:37 | Christian Grothoff | Status | new => closed |
| 2016-05-03 10:37 | Christian Grothoff | Resolution | open => won't fix |
| 2016-05-03 10:37 | Christian Grothoff | Fixed in Version | => 0.0 |
| 2016-05-03 10:37 | Christian Grothoff | Target Version | => 0.0 |