View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010116 | Taler | qtart | public | 2025-06-20 20:11 | 2025-06-21 20:02 |
| Reporter | Florian Dold | Assigned To | 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 | have not tried |
| Status | implementing | Resolution | open | ||
| Product Version | 1.0 | ||||
| Target Version | post-2.0 | ||||
| Summary | 0010116: implement direct/safe sqlite3 export on qtart (currently fails with "cannot VACUUM - SQL statements in progress") | ||||
| Description | Using "VACUUM INTO" would be the safest way to get an export of the sqlite3 DB in a proper state. However, "VACUUM INTO" fails right now, because some of the sqlite3 helpers seem to not properly reset prepared statements after use. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-06-20 20:11 | Florian Dold | New Issue | |
| 2025-06-21 20:02 | Christian Grothoff | Severity | minor => feature |
| 2025-06-21 20:02 | Christian Grothoff | Status | new => implementing |
| 2025-06-21 20:02 | Christian Grothoff | Product Version | => 1.0 |