eventsourcing
Problem: unsized queries increase the overhead for non-lazy queries
When using something like a remote SQL database for indexing, we often rely on the fact that we might not be consuming the entire ResultSet to achieve a better performance profile (or not consuming it at all).
However, this only works for truly lazy queries when nothing is extra done before the ResultSet is consumed, and the overhead of consuming the next result is low. In the SQL database scenario, even if the query itself is lazy, the moment the first result is consumed, the entire query will be fired off, and if the size of the index is substantial, there will be a delay.
Proposed solution: implement a query option for sized (limited) queries (Limit(N)). It can be ignored by truly lazy indices, but SQL-based indices can use it to optimize their queries.
