Thanks Chris. What you describe would be nice to have. However, I have a much simple problem in mind. Suppose we have a server that connects to NLMSA database to retrieve the results for a requesting client. Imagine the server returns an enormous result set. If we first go in and fetch the whole result set from the database before serving, then we are likely to timeout on the connection with the requesting client. If instead we get an iterator to the result set, we can start serving the client immediately with much smaller chance of timeout.
Here's how this helps in my case. Suppose we are doing an exploratory analysis of the data where you need to quickly check if an idea would work. You need to run a query against the database and in order to confirm the idea works you only need a small portion of the result set. In other words what I need is a LIMIT modifier on a query. Having an iterator access makes limiting trivial. Hence my question. As for the JOIN, I think it deserves a whole new discussion thread. Let's start it! Cheers, Alex --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
