View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009668 | Taler | exchange | public | 2025-03-27 15:59 | 2025-03-27 16:35 |
| Reporter | oec | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | confirmed | Resolution | open | ||
| Product Version | git (master) | ||||
| Target Version | post-1.0 | ||||
| Summary | 0009668: Potentially change the SQL versioning framework to use schema scopes for versions | ||||
| Description | Right now, SQL functions like `create_table_foo` are in a global scope. This has created friction when dropping and re-creation of a table becomes necessary. Similarly, all functions like `alter_table_foo` and `constraint_table_foo` can only exist once in the global namespace. Right now we do have workarounds by using digit-suffixes, like `alter_table_foo5`, to overcome this, and that works for `alter` and `constraint` actions, but fail for `create`. Instead, we should try and place the functions for each version into their own schema, f.e. in `0023-exchange.sql.in` starting with a `SEARCH exchange-0023;` statement. | ||||
| Additional Information | It is not clear if this approach will work easily and if the function themselves would need to be aware of the schemata and their logic get more complicated. We need to try and figures this out. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-03-27 15:59 | oec | New Issue | |
| 2025-03-27 15:59 | oec | Status | new => assigned |
| 2025-03-27 15:59 | oec | Assigned To | => Christian Grothoff |
| 2025-03-27 16:35 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2025-03-27 16:35 | Christian Grothoff | Status | assigned => confirmed |
