-
Notifications
You must be signed in to change notification settings - Fork 7
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
Unique ID identifying the catalog #609
Comments
novoj
added a commit
that referenced
this issue
Jun 18, 2024
Catalogs are uniquely identified by their name. However, this name can change using `rename' and `replace' operations on the catalog. So if we have catalogs `a` and `b`, and later `b` replaces `a` and starts using the `a` catalog name, we cannot distinguish it from the original `a` catalog. By introducing a new internally assigned UUID for each catalog, we can still distinguish catalog `a` with UUID `1` from catalog `a` with UUID 2. This internal ID can be used by the outside world to infer the identity of the catalog and be used for synchronization purposes.
novoj
added a commit
that referenced
this issue
Jun 18, 2024
Catalogs are uniquely identified by their name. However, this name can change using `rename' and `replace' operations on the catalog. So if we have catalogs `a` and `b`, and later `b` replaces `a` and starts using the `a` catalog name, we cannot distinguish it from the original `a` catalog. By introducing a new internally assigned UUID for each catalog, we can still distinguish catalog `a` with UUID `1` from catalog `a` with UUID 2. This internal ID can be used by the outside world to infer the identity of the catalog and be used for synchronization purposes.
novoj
added a commit
that referenced
this issue
Jun 18, 2024
Catalogs are uniquely identified by their name. However, this name can change using `rename' and `replace' operations on the catalog. So if we have catalogs `a` and `b`, and later `b` replaces `a` and starts using the `a` catalog name, we cannot distinguish it from the original `a` catalog. By introducing a new internally assigned UUID for each catalog, we can still distinguish catalog `a` with UUID `1` from catalog `a` with UUID 2. This internal ID can be used by the outside world to infer the identity of the catalog and be used for synchronization purposes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Catalogs are uniquely identified by their name. However, this name can change using
rename' and
replace' operations on the catalog. So if we have catalogsa
andb
, and laterb
replacesa
and starts using thea
catalog name, we cannot distinguish it from the originala
catalog. By introducing a new internally assigned UUID for each catalog, we can still distinguish cataloga
with UUID1
from cataloga
with UUID 2. This internal ID can be used by the outside world to infer the identity of the catalog and be used for synchronization purposes.The text was updated successfully, but these errors were encountered: