A row handle always belongs to a particular table, and can not be mixed between the tables, even if the tables are of the same type. Even before a row handle has been inserted into the table and after it has been removed, it still belongs to that table and can not be inserted into any other one.
Just as the tables are single-threaded, the row handles are single-threaded.
A RowHandle is created by the table's factory
$rh = $table->makeRowHandle($row) or die "$!";
The newly created row handle is not inserted in the table. To find out, whether the row handle is actually inserted in the table, use
$result = $rh->isInTable();
As a special case, a row handle may be null. It pretty much means that there is only the Perl wrapper layer of RowHandle but no actual RowHandle under it. This happens to be much more convenient than dealing with undefined values at Perl level. The null row handles are returned by the certain table calls to indicate that the requested data was not found in the table. A row handle can be checked for being null:
$result = $rh->isNull();
A null row handle may also be explicitly created with
$rh = $table->makeNullRowHandle();
As usual, the row handle references can be compared for the sameness of the actual row handle they contain:
$result = $rh1->same($rh2);
The row can be extracted from the row handle:
$row = $rh->getRow() or die "$!";
If the row handle is null, getRow() will return an undef and an error message.
The rest of the row handle methods are just a syntactic sugar for the table's iteration methods:
$rh = $rh->next(); $rh = $rh->nextIdx($idxType); $rh = $rh->firstOfGroupIdx($idxType); $rh = $rh->nextGroupIdx($idxType);
They work in exactly the same way as the table methods.
No comments:
Post a Comment