com.azalient.api.a.tables
Interface IRecord
- All Known Subinterfaces:
- IAgent, IArea, IAspect, IAttached, IBehaviour, ICentre, IChannel, IColour, IController, ICourse, ICrossing, ICrossingTime, IDiscreteDistribution, IDistribution, IDistributionBar, IDivision, IDwell, IEngine, IEngineRecord, IFeature, IFixture, IFleet, IGroup, IIncident, IIntersection, ILabel, ILane, ILink, ILoop, ILoopMultiple, IMatrixDescription, IMob, IMotor, IMotorCalibration, IMotorFollowing, IMotorType, INetPoint, INode, IPassenger, IPastable, IPedestrianCalibration, IPerson, IPersonTrip, IPersonType, IPhase, IPhaseCrossing, IPlace, IPlaceIndex, IPlan, IPluginInfo, IProfile, IReportingOption, IRestriction, IRouteClass, IRouteClassBehaviour, IScenario, ISector, ISequence, IService, IShape, ISign, ISignalDisplay, ISignalRule, ISpeedControl, ISplit, IStand, IStream, ISymbol, ITag, ITerm, ITextSize, ITimedEvent, ITrail, ITransport, ITransportTrip, ITransportType, ITrip, ITurn, IType, ITypeSet, IVehicle, IVehicleTrip, IVehicleType, IView, IVolume, IWalkway, IZone, RecordR, RecordRW, StoreRecordRW
- All Known Implementing Classes:
- AbstractRecordR, AbstractRecordRW, AbstractStoreRecordFixedName, AbstractStoreRecordIndirectName, AbstractStoreRecordRenamable, AbstractStoreRecordRenamableNumeric
public interface IRecord
Data is stored in pages, where each page is comprised of tables, and each table is comprised of records.
This is the base interface to one of those records.
Each record has a unique name which is used to look it up in the hash table that backs
the Primitive store. The name is commonly the first column in the record, but it does not have
to be.
|
Method Summary |
String |
name()
This is a string representation of the key field(s), used as a key for looking up the object in the Store. |
KEY_SEP_CHAR
static final char KEY_SEP_CHAR
- See Also:
- Constant Field Values
KEY_SEP
static final String KEY_SEP
DELETED
static final String DELETED
- See Also:
- Constant Field Values
name
String name()
- This is a string representation of the key field(s), used as a key for looking up the object in the Store.
If there is more than one key field, the string representation of the key fields are concatenated, separated by KEY_SEP.
See TypeObject.keyString(Object[])
If there are multiple key fields, the get() function should not return the concatenated name,
but the name function must be defined in the object so that the lookup function can use it.