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

Support primary key in API url, for record read, update and delete #835

Open
janblok opened this issue Dec 20, 2024 · 0 comments
Open

Support primary key in API url, for record read, update and delete #835

janblok opened this issue Dec 20, 2024 · 0 comments

Comments

@janblok
Copy link
Contributor

janblok commented Dec 20, 2024

Many rest API's have support for reading, updating and deletion based on the primary key in the API url.
Like:
http://localhost:8080/v1/rdbms/pgdb/film/42
instead of currently:
https://localhost:8080/v1/rdbms/pgdb/film?filter=id==42

While this works nicely API wise, there is one caveat related to composite primary keys, which could be resolved by ordering the primary key columns alphabetically in the url (to be separated by url friendly separator)
For example: http://localhost:8080/v1/rdbms/pgdb/theater/39;1023

@janblok janblok changed the title Primary key in API url support, for record read, update and delete Support primary key in API url, for record read, update and delete Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant