View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007374 | Taler | exchange | public | 2022-09-27 22:04 | 2022-11-04 20:52 |
Reporter | Florian Dold | Assigned To | Christian Grothoff | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Product Version | git (master) | ||||
Target Version | 0.9 | Fixed in Version | 0.9 | ||
Summary | 0007374: taler-exchange-dbinit should not cause postgres to log "ERROR" category messages | ||||
Description | Currently, we check whether the _v schema exists by doing a query against it and seeing if this results in an error or not. This results in postgres logging an "ERROR" category log message. That caused us to believe that (during some cbdc-sandbox scripting) the database was somehow broken, even though dbinit actually succeeded. Instead, we should do something like this: SELECT schema_name FROM information_schema.schemata WHERE schema_name = '_v'; | ||||
Tags | No tags attached. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2022-09-27 22:04 | Florian Dold | New Issue | |
2022-09-27 22:04 | Florian Dold | Status | new => assigned |
2022-09-27 22:04 | Florian Dold | Assigned To | => Christian Grothoff |
2022-10-18 21:24 | Christian Grothoff | Changeset attached | => gnunet master f0b91ff6 |
2022-10-18 21:24 | Christian Grothoff | Note Added: 0019228 | |
2022-10-18 21:24 | Christian Grothoff | Status | assigned => resolved |
2022-10-18 21:24 | Christian Grothoff | Resolution | open => fixed |
2022-10-18 21:24 | Christian Grothoff | Note Added: 0019229 | |
2022-10-18 21:24 | Christian Grothoff | Product Version | => git (master) |
2022-10-18 21:24 | Christian Grothoff | Fixed in Version | => 0.9 |
2022-10-18 21:24 | Christian Grothoff | Target Version | => 0.9 |
2022-10-18 21:24 | Christian Grothoff | Note Added: 0019230 | |
2022-11-04 20:52 | Christian Grothoff | Status | resolved => closed |