-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Channel renaming #536
Comments
Hi @gabm, thanks for the suggestion. I am also wondering how often (in practice) channels would be renamed... it should ideally happen fairly seldomly :) |
yes.. but making it impossible in the first place seems overly restrictive :) So I understand, at least for the time being, there is no interest in such a patch? |
Certainly there is an interest in such a patch but it will be tricky. – existing instances need to migrate their data store I just think that we have other subjects in the quetz code base that need fixing more urgently :) But if you want to tackle this, feel free! |
Currently the channel names are fixed as they are used as primary keys/ids for everything else in the DB. Would it be possible to use the current channel_name as "channel_id" and fill it with a fixed UUID for internal cross-references and add a new "channel_name" column for the public interface?
This way we could safely provide an API to rename channels...
The text was updated successfully, but these errors were encountered: