John Scoles wrote:
> Oracle doesn't have this feature so DBD::Oracle doesn't either.
> This has cropped up many times before So you can blame Oracle on that.
> Thier logic (as it was explained to me) is
>
> "How could you get the number of rows you are going to fetch without
> counting them all first?"
This makes sense to me, as it enables Oracle to continue to build the
result set on the server while piping rows to the client. It means that
the client doesn't have to wait for the server to build all the
(possibly millions) of rows from disk before it can start transferring
and processing them.
- Philip
