Timeline for CRUD API: How do you specify which fields to update?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 4, 2015 at 1:02 | audit | Close votes | |||
| Oct 4, 2015 at 1:02 | |||||
| Sep 24, 2015 at 18:03 | audit | Close votes | |||
| Sep 24, 2015 at 23:48 | |||||
| Sep 21, 2015 at 20:06 | vote | accept | Heinzi | ||
| Sep 20, 2015 at 14:23 | audit | Close votes | |||
| Sep 20, 2015 at 14:23 | |||||
| Sep 18, 2015 at 19:28 | comment | added | Lode | Allow and communicate both PUT and PATCH methods. When using PATCH, only send keys should be replaced, with PUT the whole object is replaced. | |
| Sep 14, 2015 at 1:24 | answer | added | adisembiring | timeline score: 1 | |
| Sep 13, 2015 at 18:10 | history | tweeted | twitter.com/#!/StackProgrammer/status/643124731600834560 | ||
| Sep 13, 2015 at 16:29 | answer | added | Jared Bernacchi | timeline score: 2 | |
| Sep 13, 2015 at 13:31 | answer | added | luboskrnac | timeline score: 9 | |
| Sep 13, 2015 at 11:51 | comment | added | SJuan76 | Why isn't identifier part of the person? For newly created Person instances that still are not persisted, and in the case the identifier is decided as part of the persistence mechanism, just leave it to null. As for the answer, JPA uses a version number; if you read version 23, when you update the item if the version in DB is 24 the write fails. | |
| Sep 13, 2015 at 10:58 | history | asked | Heinzi | CC BY-SA 3.0 |