Timeline for RESTful way to define an API that requires two keys to return a resource
Current License: CC BY-SA 3.0
Post Revisions
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 11, 2016 at 10:33 | comment | added | Luc Franken | What is the use case from the api consumer? That is in my opinion what you should focus on first. You now start with your existing code structure but that does not necessarily reflect the use case as the consumer. Your hierarchy might just be an implementation detail. | |
| Aug 11, 2016 at 7:22 | answer | added | Bart van Ingen Schenau | timeline score: 2 | |
| Aug 11, 2016 at 4:19 | comment | added | Stack Exchange Broke The Law |
"I do not want to have sequence numbers starting at different number for both tables." - what if they're not sequence numbers? Make the IDs A1_{seq} and A2_{seq}?
|
|
| Aug 10, 2016 at 21:11 | history | asked | TechCrunch | CC BY-SA 3.0 |