A:callback annotation is cleaner and if only one of the two approaches were chosen, much simpler when you want to read rows synchronously (while allowing you to implement:stream yourself). It also allows the caller an extra means of requesting cancellation by returning a bool (iefunc(T) (ok bool)) as opposed to cancelling the context.

True, the callback would allow one to implement streaming. I thought it's a bit much ceremony at the moment to do it in every callback, withselecting onchan<- and<-ctx.Done() and all. Needs to be done correctly and the code generator would be ideal. However, I realized with the upcoming support for generics a simple generic helper function could take care of this, too.

Today I was looking for a way to make sqlc to support streaming a large amount of data from a query to gRPC. I found the related issues and this discussion. To me a simple callback option seems like the best way to do it.
But now that generics have been out for a while, is there any more ideas around this topic?

I've just ran into this. I'm working on some maintenance work on a database and I don't know how many rows I get back. Could be 1K or 1M. I really love sqlc and the correctness it brings.

It would be really amazing to have a callback that would get fired off for each row.

What's the status here?

Since theiterator PR hasn't been merged yet, I'm curious about current best practices for handling large table queries.
What approaches are you using to select from huge tables? Ispagination the recommended solution, or are there other patterns the community has found effective?