[FOLIO-3586] Devise an upgrade approach for invalid tenant and module names Created: 19/Sep/22 Updated: 17/Jan/23 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Story | Priority: | TBD |
| Reporter: | Jakub Skoczen | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | CP: R3 2022 roadmap, CP: Roadmap backlog | ||||||||
| Development Team: | Core: Platform | ||||||||
| RCA Group: | TBD | ||||||||
| Description |
|
From Okapi 5.0 scheduled for Nolana, certain characters will in tenant and module names will be considered invalid. As such, migration issues may arise. Devise an approach to help dealing with these issues, example: 1. Provide a migration script to convert tenant and module names with invalid characters 2. Allow the system to function with existing names that contain invalid characters but prevent from creating new ones. Let people migrate the system over the course of one release. |
| Comments |
| Comment by Julian Ladisch [ 19/Sep/22 ] |
|
How to rename schema and role: https://www.postgresql.org/docs/current/sql-alterschema.html ALTER SCHEMA name RENAME TO new_name https://www.postgresql.org/docs/current/sql-alterrole.html ALTER ROLE name RENAME TO new_name |