Timeline for How to store and validate data between state transitions?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 10:01 | history | edited | CommunityBot |
Commonmark migration
|
|
| Dec 6, 2017 at 9:48 | comment | added | Emerson Cardoso | @Kevin - Thanks for your feedback. Updated my answer. If you still thinks it's useless, just keep your downvote :) | |
| Dec 6, 2017 at 9:46 | history | edited | Emerson Cardoso | CC BY-SA 3.0 |
changed answer according to comments
|
| Dec 5, 2017 at 23:41 | comment | added | Kevin | -1 Whether to use a DB or not is completely orthogonal to the question the OP asked. In some situations, persisting the data in a DB might be the best approach, and in others, it could greatly increase the complexity of the project for no real gain. And this answer does not touch on which patterns to use for validation logic at all. | |
| Aug 7, 2017 at 19:44 | review | Late answers | |||
| Aug 7, 2017 at 20:13 | |||||
| Aug 7, 2017 at 19:28 | history | answered | Emerson Cardoso | CC BY-SA 3.0 |