You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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
The text was updated successfully, but these errors were encountered: