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

Remove the model-service table #47

Closed
albertsgarde opened this issue Jul 22, 2023 · 0 comments · Fixed by #48
Closed

Remove the model-service table #47

albertsgarde opened this issue Jul 22, 2023 · 0 comments · Fixed by #48
Labels
Rust Mainly requires, or requires non-trivial Rust code

Comments

@albertsgarde
Copy link
Collaborator

It is not necessary to explicitly store which services are available for which models.
Instead, this can be calculated from which data objects a model has available.
To do this, each service provider must provide a list of necessary data objects.
When receiving a service API call, first check that the model has the necessary data objects, and if not, respond with an error message saying which are missing.
When receiving an all API call, the response JSON should contain an object for all services in the database, with the before mentioned error message for the unavailable ones.

@albertsgarde albertsgarde added the Rust Mainly requires, or requires non-trivial Rust code label Jul 22, 2023
@albertsgarde albertsgarde linked a pull request Jul 22, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Rust Mainly requires, or requires non-trivial Rust code
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant