View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007890 | Taler | libeufin (general) | public | 2023-07-22 07:49 | 2023-09-23 13:09 |
| Reporter | MS | Assigned To | MS | 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 | urgent | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.9.3 | Fixed in Version | 0.9.3 | ||
| Summary | 0007890: DB connection string needs ordinary postgres:// format. | ||||
| Description | All libeufin expects DB connection strings to have the format starting with "jdbc". This however makes difficult to pass such strings between libeufin and other components, notably the shell script (libeufin-load-sql) that loads the SQL files into the database. Another disadvantage is the passing of JDBC connection strings that rely on Unix domain sockets, because these are not user friendly. The solution is therefore to change all libeufin to accept postgres://-formatted connection strings, instead of the JDBC ones. | ||||
| Tags | No tags attached. | ||||
| I fully agree, that'll be much better! We should in fact stop using JDBC eventually, and thus certainly also jdbc:-uris. | |
| Fixing this bug would help to avoid database permission issues, because there will be always _one_ user going in the database. Right now, if the database is accessed via TCP, _some_ operations happen under the current process user instead of the one mentioned in the TCP connection string. | |
| Addressed here: 54717e5c9630a5ed8bec955f06ba4e2359e20dfc Now being tested. | |
| The new version fails when a connection string starts with "postgres:///" and accepts only "postgresql:///". It should be adapted to accept both formats. | |
| That should be fixed in this version: 48c1cc4ce7e338d14093b2e04ccd621282a451ee Documentation update is forthcoming. | |
| Yes, this seems to be fine now. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-07-22 07:49 | MS | New Issue | |
| 2023-07-22 07:49 | MS | Status | new => assigned |
| 2023-07-22 07:49 | MS | Assigned To | => MS |
| 2023-07-22 07:50 | MS | Target Version | => 0.9.4 |
| 2023-07-23 14:47 | Christian Grothoff | Note Added: 0020359 | |
| 2023-07-24 09:12 | MS | Target Version | 0.9.4 => 0.9.3 |
| 2023-07-24 09:20 | MS | Note Added: 0020368 | |
| 2023-07-24 09:38 | Christian Grothoff | Priority | normal => urgent |
| 2023-07-24 09:38 | Christian Grothoff | Product Version | => git (master) |
| 2023-07-25 15:14 | MS | Status | assigned => feedback |
| 2023-07-25 15:14 | MS | Note Added: 0020383 | |
| 2023-07-28 14:59 | MS | Note Added: 0020385 | |
| 2023-07-28 15:00 | MS | Note Edited: 0020385 | |
| 2023-07-28 15:15 | MS | Note Added: 0020386 | |
| 2023-08-28 10:49 | Christian Grothoff | Status | feedback => informing |
| 2023-08-28 10:49 | Christian Grothoff | Resolution | open => fixed |
| 2023-08-28 10:49 | Christian Grothoff | Fixed in Version | => 0.9.3 |
| 2023-08-28 10:49 | Christian Grothoff | Note Added: 0020447 | |
| 2023-09-23 13:09 | Christian Grothoff | Status | informing => closed |