• System.Object
  • ThinkGeo.Core.TransactionBuffer

TransactionBuffer()

• This is the class constructor.

• This is the default constructor and is typically not used.

TransactionBuffer(Dictionary<String,Feature>,Collection<String>,Dictionary<String,Feature>)

• N/A

• N/A

• addBuffer
  • Type:Dictionary<String,Feature>
  • Description:N/A

• deleteBuffer
  • Type:Collection<String>
  • Description:N/A

• editBuffer
  • Type:Dictionary<String,Feature>
  • Description:N/A

Clear()

• N/A

• This method will clear all the items in AddBuffer, EditBuffer and DeleteBuffer.

• Type:Void
• Description:None.

AddFeature(Feature)

• N/A

• None

• Type:Void
• Description:None

• feature
  • Type:Feature
  • Description:This parameter represents the Feature you are adding to the transaction buffer.

AddFeature(BaseShape)

• N/A

• None

• Type:Void
• Description:None

• baseShape
  • Type:BaseShape
  • Description:This parameter represents the shape to be added.

AddFeature(BaseShape,Dictionary<String,String>)

• N/A

• N/A

• Type:Void
• Description:N/A

• baseShape
  • Type:BaseShape
  • Description:N/A

• columnValues
  • Type:Dictionary<String,String>
  • Description:N/A

DeleteFeature(String)

• N/A

• This does not remove a feature from the TransactionBuffer but rather it add a “to be deleted record”. In this way when the TransactionBuffer if processed we know what records need to be deleted.

• Type:Void
• Description:None

• featureId
  • Type:String
  • Description:This parameter represents the unique Id for the specific Feature being passed in.

EditFeature(Feature)

• N/A

• None

• Type:Void
• Description:None

• feature
  • Type:Feature
  • Description:This parameter represents the Feature to be updated.

EditFeature(BaseShape)

• N/A

• None

• Type:Void
• Description:None

• baseShape
  • Type:BaseShape
  • Description:This parameter represents the shape to be updated. The shape ID should be the same as the feature you are going to update.

EditFeature(BaseShape,Dictionary<String,String>)

• N/A

• N/A

• Type:Void
• Description:N/A

• baseShape
  • Type:BaseShape
  • Description:N/A

• columnValues
  • Type:Dictionary<String,String>
  • Description:N/A

AddColumn(FeatureSourceColumn)

• N/A

• N/A

• Type:Void
• Description:N/A

• featureSourceColumn
  • Type:FeatureSourceColumn
  • Description:N/A

DeleteColumn(String)

• N/A

• N/A

• Type:Void
• Description:N/A

• columnName
  • Type:String
  • Description:N/A

UpdateColumn(String,FeatureSourceColumn)

• N/A

• N/A

• Type:Void
• Description:N/A

• columnName
  • Type:String
  • Description:N/A

• newFeatureSourceColumn
  • Type:FeatureSourceColumn
  • Description:N/A

GetType()

• N/A

• N/A

• Type:Type
• Description:N/A

ToString()

• N/A

• N/A

• Type:String
• Description:N/A

Equals(Object)

• N/A

• N/A

• Type:Boolean
• Description:N/A

• obj
  • Type:Object
  • Description:N/A

GetHashCode()

• N/A

• N/A

• Type:Int32
• Description:N/A

MemberwiseClone()

• N/A

• N/A

• Type:Object
• Description:N/A

Finalize()

• N/A

• N/A

• Type:Void
• Description:N/A

AddBuffer

• N/A

• It is recommended that you use this dictionary for reviewing and not for adding new items. The reason is that the Add, Delete and Edit methods to various validation checks. For example if you call the DeleteFeature twice it will handle the case that you really only want to delete the record once. Another example is if you edit a record twice it will replace the existing edit with the new one.

• Type:Dictionary<String,Feature>

DeleteBuffer

• N/A

• It is recommended that you use this dictionary for reviewing and not for adding new items. The reason is that the Add, Delete and Edit methods to various validation checks. For example if you call the DeleteFeature twice it will handle the case that you really only want to delete the record once. Another example is if you edit a record twice it will replace the existing edit with the new one.

• Type:Collection<String>

EditBuffer

• N/A

• It is recommended that you use this dictionary for reviewing and not for adding new items. The reason is that the Add, Delete and Edit methods to various validation checks. For example if you call the DeleteFeature twice it will handle the case that you really only want to delete the record once. Another example is if you edit a record twice it will replace the existing edit with the new one.

• Type:Dictionary<String,Feature>

AddColumnBuffer

• N/A

• N/A

• Type:Collection<FeatureSourceColumn>

DeleteColumnBuffer

• N/A

• N/A

• Type:Collection<String>

UpdateColumnBuffer

• N/A

• N/A

• Type:Dictionary<String,FeatureSourceColumn>