X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=lib%2FZOOM.pod;h=2ea8eea4eb3fda958b8e788783928f35adb4b4cd;hb=c397598e5bbb9f2347730f992210fbfa5083a35d;hp=6c76b19759baf77a4f978378a58bf77ffc90a9e8;hpb=e862553c363986551651c42fa9a8afc6355f5b5b;p=ZOOM-Perl-moved-to-github.git diff --git a/lib/ZOOM.pod b/lib/ZOOM.pod index 6c76b19..2ea8eea 100644 --- a/lib/ZOOM.pod +++ b/lib/ZOOM.pod @@ -1,4 +1,4 @@ -# $Id: ZOOM.pod,v 1.44 2007-09-14 10:35:02 mike Exp $ +# $Id: ZOOM.pod,v 1.46 2007-12-10 21:51:40 mike Exp $ use strict; use warnings; @@ -545,7 +545,7 @@ Returns the number of records in the result set. The C method returns a C object representing a record from result-set, whose position is indicated by the argument passed in. This is a zero-based index, so that legitimate values -range from zero to C<$rs->size()-1>. +range from zero to C<$rs-Esize()-1>. The C API is identical, but it never invokes a network operation, merely returning the record from the ResultSet's @@ -571,7 +571,7 @@ wants to display a whole list of results. Conversely, the software's strategy might be always to ask for blocks of a twenty records: that's great for assembling long lists of things, but wasteful when only one record is wanted. The problem is that the ZOOM module can't -tell, when you call C<$rs->record()>, what your intention is. +tell, when you call C<$rs-Erecord()>, what your intention is. But you can tell it. The C method fetches a sequence of records, all in one go. It takes three arguments: the first is the