Skip to content
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

Closed
novoj opened this issue Jun 18, 2024 · 0 comments · Fixed by #613
Closed

Unique ID identifying the catalog #609

novoj opened this issue Jun 18, 2024 · 0 comments · Fixed by #613
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@novoj
Copy link
Collaborator

novoj commented 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 novoj added the enhancement New feature or request label Jun 18, 2024
@novoj novoj added this to the Beta milestone Jun 18, 2024
@novoj novoj self-assigned this Jun 18, 2024
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 novoj linked a pull request Jun 18, 2024 that will close this issue
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.
@lukashornych lukashornych reopened this Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants