FDO .NET API Reference Feature Data Objects

OSGeo::FDO::Commands::Locking::ILockConflictReaderImp Class Reference
[OSGeo::FDO::Commands::Locking]

Inherits OSGeo::FDO::Runtime::Disposable, and OSGeo::FDO::Commands::Locking::ILockConflictReader.

Inheritance diagram for OSGeo::FDO::Commands::Locking::ILockConflictReaderImp:

Inheritance graph
[legend]
List of all members.

Detailed Description

The ILockConflictReaderImp class is a concrete implementation of ILockConflictReaderImp. The ILockConflictReader interface provides forward only, read-only functionality for identifying features that have a lock conflict. Features with a lock conflict are those that the caller is attempting to modify that are already locked by someone else.

()

Remarks:
A reference to an ILockConflictReader is returned from the IAcquireLock, ISelect, IReleaseLock, IUpdate, and IDelete commands. The initial position of the ILockConflictReader is prior to the first item, thus you must call ReadNext to begin accessing any data.

Definition at line 44 of file mgILockConflictReaderImp.h.


Public Member Functions

System::Void Close ()
 Closes the ILockConflictReader object, freeing any resources it may be holding.
OSGeo::FDO::Commands::Locking::ConflictType GetConflictType ()
 Gets the conflict type for the conflict currently being read.
System::String * GetFeatureClassName ()
 Gets the class name of the feature currently being read.
OSGeo::FDO::Commands::PropertyValueCollectionGetIdentity ()
 Returns an PropertyValueCollection containing the property values that uniquely identify the feature currently being read.
System::String * GetLockOwner ()
 Gets the name of the owner who holds a lock on the feature currently being read.
System::String * GetLongTransaction ()
 Gets the name of the long transaction in which the feature currently being read is locked.
System::Boolean ReadNext ()
 Advances the reader to the next item. The default position of the reader is prior to the first item. Thus, you must call ReadNext to begin accessing any data.

Comments or suggestions? Send us feedback.