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

Retrieving Collections and Resources by multiple identifiers #4

Open
adamretter opened this issue Oct 25, 2019 · 3 comments
Open

Retrieving Collections and Resources by multiple identifiers #4

adamretter opened this issue Oct 25, 2019 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@adamretter
Copy link
Contributor

adamretter commented Oct 25, 2019

In eXist-db Collections and Documents may be retrieved by their database path. However these Collections and Documents also have a numerical identifier.

In FusionDB in addition to Collections and Documents having a path and a numerical identifier, they also have a UUID. In FusionDB a Collection or Document can be retrieved directly just by its UUID.

It would be nice if we could retrieve Collections and Documents directly by an identifier. By directly, I mean without having to necessarily access a Document or Sub-Collection through a parent Collection.

One option perhaps could be as simple as swapping out String id in the XML:DB API for an interface like Identifier id. This would allow implementations to define their own identifiers, and allow retrieval by multiple different types of identifiers?

@adamretter adamretter changed the title Retrieving Collection and Resources by multiple identifiers Retrieving Collections and Resources by multiple identifiers Oct 25, 2019
@reinhapa
Copy link
Contributor

Sounds reasonable. How would we handle the backwards compatibility in that case? Creating a default String based implementation?

@adamretter
Copy link
Contributor Author

@reinhapa I guess if we want API backwards compatibility then we have to add new methods alongside the existing String id methods

@reinhapa reinhapa self-assigned this Dec 9, 2019
@reinhapa reinhapa added the enhancement New feature or request label Dec 9, 2019
@reinhapa
Copy link
Contributor

reinhapa commented Dec 9, 2019

One option perhaps could be as simple as swapping out String id in the XML:DB API for an interface like Identifier id. This would allow implementations to define their own identifiers, and allow retrieval by multiple different types of identifiers?

@adamretter I could imagine to add a new method to either the Database in order to createIdentifier() implementation of a global document id...

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

No branches or pull requests

2 participants