Timeline for What is this (anti?)pattern called? (or how to describe it)
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 8, 2019 at 6:00 | answer | added | Matthias | timeline score: 1 | |
| Aug 8, 2013 at 17:36 | vote | accept | Alex Celeste | ||
| Aug 8, 2013 at 11:42 | comment | added | Ben Lee | And don't forget ORM method chaining, which is either an instance of this or something very similar. You start with an object and then run methods like "where", "order_by", etc..., but it doesn't evaluate the query until you actually request data. In the background, it progressively builds a query to be evaluated later. Lazy evaluation is definitely a good pattern here, because it limits the number of database calls. | |
| Aug 8, 2013 at 10:32 | comment | added | AndreasScheinert | Besides lazy evaluation maybe this could also be described as late binding? | |
| Aug 8, 2013 at 9:23 | answer | added | Jörg W Mittag | timeline score: 6 | |
| Aug 8, 2013 at 4:40 | answer | added | greyfade | timeline score: 9 | |
| Aug 8, 2013 at 4:22 | comment | added | James Anderson | In this C++ world this would be called "normal". | |
| Aug 8, 2013 at 4:10 | review | First posts | |||
| Aug 8, 2013 at 6:25 | |||||
| Aug 8, 2013 at 4:03 | comment | added | user40980 | Please flag for migration instead of reposting. It helps keeps comments (which may contain clarifications) together. Sometimes, a question isn't appropriate for the target site and the moderators can help explain why rather than having closed/deleted questions on multiple sites. | |
| Aug 8, 2013 at 3:51 | history | asked | Alex Celeste | CC BY-SA 3.0 |