Are SQL queries usually eager or lazy? i.e. does db compute once and then you page through results; or does it compute as you request pages?
@fdaapproved @hadleywickham anything that does anything interesting with full table scans (which is most queries) will need to be eager, no?
-
-
@avibryant@fdaapproved what if the results are too big too fit in memory? The more I think about the more I realise I don't understand -
@hadleywickham@fdaapproved I know from working with map reduce that most things can be modeled as merge sorts and single-pass scans.
End of conversation
New conversation -
-
-
@avibryant@hadleywickham agreed, but dollars to donuts someone is lazy about function eval in the column listThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@avibryant@hadleywickham most sorts would also need to be eager -
@avibryant@hadleywickham I do now sort of wonder what SELECT *,NOW() does when the query takes time?
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.