Timeline for How much of the data preparation, transformation, and processing belongs in Repository layer?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 29, 2016 at 9:09 | comment | added | kayess | Well, if you have a clearly defined use case it's good as it reflects a business use case. You could although implement it in a way that clearly communicates the business use case that could utilise commands and queries. The "display values for that product" is definitely a query, which you could decorate with formatting, etc. | |
| Nov 28, 2016 at 21:30 | comment | added | Dennis | user selects a product, values for product are created and are written to the database for a particular order. After that, every time the order is pulled up in the system, those values are displayed. It's not reporting really but... viewing an order. Use case may be called "Display an order". part of that use case is "display values for that product". In a way all of the above is just a complicated way to show values as part of that use case | |
| Nov 28, 2016 at 21:23 | vote | accept | Dennis | ||
| Nov 28, 2016 at 20:03 | history | edited | kayess | CC BY-SA 3.0 |
added 414 characters in body
|
| Nov 28, 2016 at 19:40 | history | answered | kayess | CC BY-SA 3.0 |