Timeline for How to calculate a list of users ranked by question favorite count totals.
Current License: CC BY-SA 2.5
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 18, 2020 at 8:33 | history | edited | CommunityBot |
Commonmark migration
|
|
Aug 18, 2010 at 15:01 | comment | added | Sky Sanders |
sound decision. I took another approach: all api objects are 'stubs' by default. If the query in question returns full objects, i clear the IsStub flag, recursively. Subsequently, upon first access, if a stub and lazy loading is enabled on the context, the object is fetched. In some cases this can add up to a lot of requests, so the context has an eager loading option, wherein when a page of objects are retrieved, all of the stubs are fetched in a single batch, so a request for a page of 100 questions (w body/answers/comments) would result in 2 requests and return all the data.
|
|
Aug 18, 2010 at 14:20 | comment | added | Dave DeLong | @code poet yeah, definitely. one of the design decisions i made w/ my wrapper is that a request only returns data of a single type. so even though requesting a question returns user information, i only return the question info itself. that means that i have to do the extra request at the end for all the user info, but also means i don't have partially created User objects floating around. | |
Aug 18, 2010 at 14:18 | history | edited | Dave DeLong | CC BY-SA 2.5 |
added code comments
|
Aug 18, 2010 at 2:12 | comment | added | Sky Sanders | thanks dave. it is very interesting to see implementations of familiar code in other lanquages/libraries, kinda like a rosetta stone of sorts. | |
Aug 17, 2010 at 22:03 | history | edited | Dave DeLong | CC BY-SA 2.5 |
added 969 characters in body
|
Aug 17, 2010 at 20:56 | history | answered | Dave DeLong | CC BY-SA 2.5 |