You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Hi @gabm, thanks for the suggestion.
We actually do have the same problem with the package store (where we also use the channel name as "folder" to store the files in).
So it would break a couple of assumptions that are in the code base currently.
I am also wondering how often (in practice) channels would be renamed... it should ideally happen fairly seldomly :)
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: