Timeline for Web API best practices inserting data: nested or per entity
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 26, 2018 at 9:10 | vote | accept | Zeep | ||
| Jan 23, 2018 at 21:21 | answer | added | Low Flying Pelican | timeline score: 1 | |
| Jan 23, 2018 at 17:55 | comment | added | Robert Harvey | I would think the driver for that is, what do you want your API to look like? | |
| Jan 23, 2018 at 16:58 | answer | added | Ewan | timeline score: 1 | |
| Jan 23, 2018 at 16:55 | history | edited | Zeep | CC BY-SA 3.0 |
added 99 characters in body
|
| Jan 23, 2018 at 16:53 | comment | added | Zeep | What I mean is, do I allow the user to send data of all 3 entities nested in 1 post object at once, or do I want the customer to first insert a Manual record, followed by a Version record and then eventually a Document record? I only want customers to send data, I won't be inserting or updating data on their end. | |
| Jan 23, 2018 at 16:46 | comment | added | Robert Harvey |
Should I store his reference numbers or should he store mine for future updates, deletes and related inserts? -- That depends on whether you need to access his database, or he needs to access yours, or both.
|
|
| Jan 23, 2018 at 16:45 | comment | added | Robert Harvey | I don't understand this question: "Do I accept the posted data object in a nested XML/Json structure, or do I want the customers to add the data entity per entity?" Can you clarify? | |
| Jan 23, 2018 at 16:26 | history | asked | Zeep | CC BY-SA 3.0 |