Rogue Wave banner
Previous fileTop of DocumentContentsIndexNext file

RWDBBulkReader



Data Type and Member Function Indexes
(exclusive of constructors and destructors)

Synopsis

#include <rw/db/bkread.h>
#include <rw/db/select.h>
#include <rw/db/table.h>

RWDBBulkReader reader1 = table.bulkReader(connection);
RWDBBulkReader reader2 = selector.bulkReader(connection);

Description

Like RWDBReader, RWDBBulkReader is a class designed to read result sets associated with an RWDBTable or RWDBSelector. The main difference between RWDBBulkReader and RWDBReader is that arrays of values are shifted into the RWDBBulkReader for each column in the result set, while scalar values are shifted out of the RWDBReader. These arrays are passed by reference and need to stay in scope for the duration of the reader. The classes RWDBVector<T>, RWDBDateVector, RWDBStringVector, and RWDBBinaryVector are used for reading simple numeric types, dates, strings, and binary data, respectively.

RWDBBulkReader is designed around the Interface/Implementation paradigm. An RWDBBulkReader instance is an interface to a reference-counted implementation; copy constructors and assignment operators produce additional references to a shared implementation. An RWDBBulkReader implementation is a base class from which a family of database-specific implementations is derived.

Example

The following example uses an RWDBBulkReader to read a result set, where the first column is a date and the second column is an integer.

Public Constructors

RWDBBulkReader();
RWDBBulkReader(const RWDBBulkReader& rdr);

Public Member Operator

RWDBBulkReader&
operator=(const RWDBBulkReader& rdr);
RWDBBulkReader&
operator[](size_t index);
RWDBBulkReader &
operator<<(RWDBAbstractBuffer& val);
RWDBBulkReader &
operator<<(RWDBDateVector& dateVector);
size_t 
operator()();

Public Member Functions

int 
cancel();
RWBoolean 
isValid() const;
RWDBStatus
status() const;


Previous fileTop of DocumentContentsIndexNext file

©Copyright 1999, Rogue Wave Software, Inc.
Contact Rogue Wave about documentation or support issues.