Documented use of cursor->next for fast but uncomfortable data fetches

[dbsrgits/DBIx-Class.git] / lib / DBIx / Class / Storage / DBI / Cursor.pm

diff --git a/lib/DBIx/Class/Storage/DBI/Cursor.pm b/lib/DBIx/Class/Storage/DBI/Cursor.pm
index a63b2a6..d2aa347 100644 (file)
--- a/lib/DBIx/Class/Storage/DBI/Cursor.pm
+++ b/lib/DBIx/Class/Storage/DBI/Cursor.pm
@@ -30,8 +30,6 @@ information.
 
 =head2 new
 
-=back
-
 Returns a new L<DBIx::Class::Storage::DBI::Cursor> object.
 
 =cut
@@ -63,7 +61,8 @@ sub new {
 
 =back
 
-Advances the cursor to the next row and returns an arrayref of column values.
+Advances the cursor to the next row and returns an array of column
+values (the result of L<DBI/fetchrow_array> method).
 
 =cut
 
@@ -123,8 +122,6 @@ sub all {
 
 =head2 reset
 
-=back
-
 Resets the cursor to the beginning of the L<DBIx::Class::ResultSet>.
 
 =cut
@@ -164,7 +161,7 @@ sub DESTROY {
   my ($self) = @_;
 
   $self->_check_forks_threads;
-  $self->{sth}->finish if $self->{sth}->{Active};
+  $self->{sth}->finish if $self->{sth} && $self->{sth}->{Active};
 }
 
 1;