C:/Sateda/records.dat.
@author Sebastian
The unit of data of the Amazon Kinesis stream, which is composed of a sequence number, a partition key, and a data blob.
Record record = store.getRecord(store.getAt(0)); record.set("foo", "bar"); List<Record> modified = store.getModifiedRecords(); for (Record r : modified) { } store.commitChanges();
key - record key state - record state ('N' new, 'U' update, 'D' deleted) content - record the blackberry contactuid
Experimental API: This class is still under rapid development, and is very likely to be deleted. Use it at your own risk.
An entry in a {@link com.google.gwt.valuestore.shared.ValueStore ValueStore}.Individual DataComponents may also look for special properties on Records which control styling or behavior for those records, such as {@link com.smartgwt.client.widgets.grid.ListGrid#setRecordEditProperty(String)}
For efficient data exchange, a record that is read from any source holds its data in serialized binary form. Fields are deserialized lazily upon first access. Modified fields are cached and the modifications are incorporated into the binary representation upon the next serialization or any explicit call to the {@link #updateBinaryRepresenation()} method.
IMPORTANT NOTE: Records must be used as mutable objects and be reused across user function calls in order to achieve performance. The record is a heavy-weight object, designed to minimize calls to the individual fields' serialization and deserialization methods. It holds quite a bit of state consumes a comparably large amount of memory (> 200 bytes in a 64 bit JVM) due to several pointers and arrays.
This class is NOT thread-safe!
Records are added to a {@link net.sf.jpluck.palm.Database}. The database iterates through these records and writes their IDs and data to a PDB. @see net.sf.jpluck.palm.Database
A object implementing the record interface is essentially a so called "dynamic bean".
This interface inherits from RecordData which provides further data access methods.
The Record interface is implemented by the class {@link org.apache.empire.db.DBRecord}
For efficient data exchange, a record that is read from any source holds its data in serialized binary form. Fields are deserialized lazily upon first access. Modified fields are cached and the modifications are incorporated into the binary representation upon the next serialization or any explicit call to the {@link #updateBinaryRepresenation()} method.
IMPORTANT NOTE: Records must be used as mutable objects and be reused across user function calls in order to achieve performance. The record is a heavy-weight object, designed to minimize calls to the individual fields' serialization and deserialization methods. It holds quite a bit of state consumes a comparably large amount of memory (> 200 bytes in a 64 bit JVM) due to several pointers and arrays.
This class is NOT thread-safe!
{@link SelectQuery}
@author Lukas Eder
@see SelectQuery#getResult()
A Record can be instantiated via {@link Repository#newRecord() Repository.newRecord} or retrieved via{@link Repository#read(RecordId) Repository.read}. As all entities within this API, records are dumb data objects.
All Record-related CRUD operations are available on the {@link Repository} interface:{@link Repository#create(Record) Create}, {@link Repository#read(RecordId) Read}, {@link Repository#update(Record) Update}, {@link Repository#delete(RecordId) Delete}.
A Record object is not necessarily a representation of a complete record. When {@link Repository#read(RecordId,java.util.List) reading}a record, you can specify to only read certain fields. Likewise, when {@link Repository#update(Record) updating}, you only need to put the fields in this object that you want to be updated. But it is not necessary to remove unchanged fields from this object, the repository will compare with the current situation and ignore unchanged fields.
Since for an update, this object only needs to contain the fields you want to update, fields that are not in this object will not be automatically removed from the record. Rather, you have to say explicitly which fields should be deleted by adding them to the {@link #getFieldsToDelete() fields-to-delete} list. If thefields-to-delete list contains field names that do not exist in the record, then these will be ignored upon update, rather than causing an exception.
The {@link RecordType} and its version define the schema of the record. As is explained in more detail inLily's repository model documentation, a record has a pointer to three (possibly) different record types, one for each scope.
Contains the raw bytes for a Record in a PDB.
Note that it is not associated with a Record number or ID.
Record represents a set of Attributes. It's used in Table class. It can represent various types of data, e.g. user settings, config parameters etc. When used in Table, different records might have different attributes -- attributes with different names.
@author Logica Mobile Networks SMPP Open Source Team
@version $Revision: 1.2 $
@see Table
@see Attribute
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |