Class RelationDefinitionHeadingLinkRows

Heading link table for RelDef, for MDO headers Collection of RelationDefinitionHeadingLinkRow. Each element of the collection represents one row in the RelationDefinitionHeadingLink table.

Inheritance
Object
NestedPersist
NestedPersistFacade
NestedCollectionPersist
TableRowsBase
RelationDefinitionHeadingLinkRows
Inherited Members
Namespace: SuperOffice.CRM.Rows
Assembly: SoDataBase.dll
Syntax
public class RelationDefinitionHeadingLinkRows : TableRowsBase, INestedPersist, IEnumerable<INestedPersist>, ISoCollection, IEnumerable, IList, ICollection, INotifyCollectionChanged, IBindingList
Remarks

Row collections can be created in several ways.

  • Use the static CreateNew() method to create a new, empty collection. You can then add objects of type RelationDefinitionHeadingLinkRow to it, and use methods like to operate on the whole collection.
  • You can create a (nested) RelationDefinitionHeadingLinkRows RelationDefinitionHeadingLinkRows.CustomSearch object to obtain a query pre-populated with the correct tableinfo and return fields. This query can be modified with restrictions, etc. Then, use the static GetFromCustomSearch(RelationDefinitionHeadingLinkRows.CustomSearch) method to apply the query to the database and obtain the result as a Rows object, with one item for each table row that matched your query.
  • For each non-unique index defined for the table, there is a corresponding GetFromIdx method to make retrieving data via the indexes easy.
Unique indexes are handled through the RelationDefinitionHeadingLinkRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a GetFromReader(SoDataReader, RelationDefinitionHeadingLinkTableInfo) method to retrieve the results of queries that return more than one row (this method will iterate over the reader to fetch ALL results, so beware of fetching huge result sets).

Properties

Item[Int32]

Get a RelationDefinitionHeadingLinkRow given its index in the collection.

Declaration
public RelationDefinitionHeadingLinkRow this[int index] { get; }
Parameters
Type Name Description
Int32 index

Index of the RelationDefinitionHeadingLinkRow in the collection
Property Value
Type Description
RelationDefinitionHeadingLinkRow
Remarks

Row collections can be created in several ways.

  • Use the static CreateNew() method to create a new, empty collection. You can then add objects of type RelationDefinitionHeadingLinkRow to it, and use methods like to operate on the whole collection.
  • You can create a (nested) RelationDefinitionHeadingLinkRows RelationDefinitionHeadingLinkRows.CustomSearch object to obtain a query pre-populated with the correct tableinfo and return fields. This query can be modified with restrictions, etc. Then, use the static GetFromCustomSearch(RelationDefinitionHeadingLinkRows.CustomSearch) method to apply the query to the database and obtain the result as a Rows object, with one item for each table row that matched your query.
  • For each non-unique index defined for the table, there is a corresponding GetFromIdx method to make retrieving data via the indexes easy.
Unique indexes are handled through the RelationDefinitionHeadingLinkRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a GetFromReader(SoDataReader, RelationDefinitionHeadingLinkTableInfo) method to retrieve the results of queries that return more than one row (this method will iterate over the reader to fetch ALL results, so beware of fetching huge result sets).

Methods

Add(RelationDefinitionHeadingLinkRow)

Add one RelationDefinitionHeadingLinkRow to the collection.

Declaration
public int Add(RelationDefinitionHeadingLinkRow row)
Parameters
Type Name Description
RelationDefinitionHeadingLinkRow row

An instance of RelationDefinitionHeadingLinkRow to be added to the collection.
Returns
Type Description
Int32

The index of the added RelationDefinitionHeadingLinkRow.
Remarks

Row collections can be created in several ways.

  • Use the static CreateNew() method to create a new, empty collection. You can then add objects of type RelationDefinitionHeadingLinkRow to it, and use methods like to operate on the whole collection.
  • You can create a (nested) RelationDefinitionHeadingLinkRows RelationDefinitionHeadingLinkRows.CustomSearch object to obtain a query pre-populated with the correct tableinfo and return fields. This query can be modified with restrictions, etc. Then, use the static GetFromCustomSearch(RelationDefinitionHeadingLinkRows.CustomSearch) method to apply the query to the database and obtain the result as a Rows object, with one item for each table row that matched your query.
  • For each non-unique index defined for the table, there is a corresponding GetFromIdx method to make retrieving data via the indexes easy.
Unique indexes are handled through the RelationDefinitionHeadingLinkRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a GetFromReader(SoDataReader, RelationDefinitionHeadingLinkTableInfo) method to retrieve the results of queries that return more than one row (this method will iterate over the reader to fetch ALL results, so beware of fetching huge result sets).

AddNew()

Add a new instance of RelationDefinitionHeadingLinkRow added to the collection.

Declaration
public RelationDefinitionHeadingLinkRow AddNew()
Returns
Type Description
RelationDefinitionHeadingLinkRow

A new instance of RelationDefinitionHeadingLinkRow added to the collection.
Remarks

Row collections can be created in several ways.

  • Use the static CreateNew() method to create a new, empty collection. You can then add objects of type RelationDefinitionHeadingLinkRow to it, and use methods like to operate on the whole collection.
  • You can create a (nested) RelationDefinitionHeadingLinkRows RelationDefinitionHeadingLinkRows.CustomSearch object to obtain a query pre-populated with the correct tableinfo and return fields. This query can be modified with restrictions, etc. Then, use the static GetFromCustomSearch(RelationDefinitionHeadingLinkRows.CustomSearch) method to apply the query to the database and obtain the result as a Rows object, with one item for each table row that matched your query.
  • For each non-unique index defined for the table, there is a corresponding GetFromIdx method to make retrieving data via the indexes easy.
Unique indexes are handled through the RelationDefinitionHeadingLinkRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a GetFromReader(SoDataReader, RelationDefinitionHeadingLinkTableInfo) method to retrieve the results of queries that return more than one row (this method will iterate over the reader to fetch ALL results, so beware of fetching huge result sets).

AddRange(IEnumerable<RelationDefinitionHeadingLinkRow>)

Add a range of RelationDefinitionHeadingLinkRow to the collection.

Declaration
public RelationDefinitionHeadingLinkRows AddRange(IEnumerable<RelationDefinitionHeadingLinkRow> rows)
Parameters
Type Name Description
IEnumerable<RelationDefinitionHeadingLinkRow> rows
Returns
Type Description
RelationDefinitionHeadingLinkRows

The updated RelationDefinitionHeadingLinkRows collection object.
Remarks

Row collections can be created in several ways.

  • Use the static CreateNew() method to create a new, empty collection. You can then add objects of type RelationDefinitionHeadingLinkRow to it, and use methods like to operate on the whole collection.
  • You can create a (nested) RelationDefinitionHeadingLinkRows RelationDefinitionHeadingLinkRows.CustomSearch object to obtain a query pre-populated with the correct tableinfo and return fields. This query can be modified with restrictions, etc. Then, use the static GetFromCustomSearch(RelationDefinitionHeadingLinkRows.CustomSearch) method to apply the query to the database and obtain the result as a Rows object, with one item for each table row that matched your query.
  • For each non-unique index defined for the table, there is a corresponding GetFromIdx method to make retrieving data via the indexes easy.
Unique indexes are handled through the RelationDefinitionHeadingLinkRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a GetFromReader(SoDataReader, RelationDefinitionHeadingLinkTableInfo) method to retrieve the results of queries that return more than one row (this method will iterate over the reader to fetch ALL results, so beware of fetching huge result sets).

CreateChild()

Create a new instance of RelationDefinitionHeadingLinkRow

Declaration
protected override TableRowBase CreateChild()
Returns
Type Description
TableRowBase

New instance of RelationDefinitionHeadingLinkRow
Overrides
Remarks

Row collections can be created in several ways.

  • Use the static CreateNew() method to create a new, empty collection. You can then add objects of type RelationDefinitionHeadingLinkRow to it, and use methods like to operate on the whole collection.
  • You can create a (nested) RelationDefinitionHeadingLinkRows RelationDefinitionHeadingLinkRows.CustomSearch object to obtain a query pre-populated with the correct tableinfo and return fields. This query can be modified with restrictions, etc. Then, use the static GetFromCustomSearch(RelationDefinitionHeadingLinkRows.CustomSearch) method to apply the query to the database and obtain the result as a Rows object, with one item for each table row that matched your query.
  • For each non-unique index defined for the table, there is a corresponding GetFromIdx method to make retrieving data via the indexes easy.
Unique indexes are handled through the RelationDefinitionHeadingLinkRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a GetFromReader(SoDataReader, RelationDefinitionHeadingLinkTableInfo) method to retrieve the results of queries that return more than one row (this method will iterate over the reader to fetch ALL results, so beware of fetching huge result sets).

CreateNew()

Create a new instance of the RelationDefinitionHeadingLinkRows object. This collection will contain no rows.

Declaration
public static RelationDefinitionHeadingLinkRows CreateNew()
Returns
Type Description
RelationDefinitionHeadingLinkRows

A new instance of the RelationDefinitionHeadingLinkRows object.
Remarks

Row collections can be created in several ways.

  • Use the static CreateNew() method to create a new, empty collection. You can then add objects of type RelationDefinitionHeadingLinkRow to it, and use methods like to operate on the whole collection.
  • You can create a (nested) RelationDefinitionHeadingLinkRows RelationDefinitionHeadingLinkRows.CustomSearch object to obtain a query pre-populated with the correct tableinfo and return fields. This query can be modified with restrictions, etc. Then, use the static GetFromCustomSearch(RelationDefinitionHeadingLinkRows.CustomSearch) method to apply the query to the database and obtain the result as a Rows object, with one item for each table row that matched your query.
  • For each non-unique index defined for the table, there is a corresponding GetFromIdx method to make retrieving data via the indexes easy.
Unique indexes are handled through the RelationDefinitionHeadingLinkRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a GetFromReader(SoDataReader, RelationDefinitionHeadingLinkTableInfo) method to retrieve the results of queries that return more than one row (this method will iterate over the reader to fetch ALL results, so beware of fetching huge result sets).

Find(Predicate<RelationDefinitionHeadingLinkRow>)

Apply the predicate to each element of the collection and return the first row that matches; if no match then return null

Declaration
public RelationDefinitionHeadingLinkRow Find(Predicate<RelationDefinitionHeadingLinkRow> condition)
Parameters
Type Name Description
Predicate<RelationDefinitionHeadingLinkRow> condition
Returns
Type Description
RelationDefinitionHeadingLinkRow
Remarks

Row collections can be created in several ways.

  • Use the static CreateNew() method to create a new, empty collection. You can then add objects of type RelationDefinitionHeadingLinkRow to it, and use methods like to operate on the whole collection.
  • You can create a (nested) RelationDefinitionHeadingLinkRows RelationDefinitionHeadingLinkRows.CustomSearch object to obtain a query pre-populated with the correct tableinfo and return fields. This query can be modified with restrictions, etc. Then, use the static GetFromCustomSearch(RelationDefinitionHeadingLinkRows.CustomSearch) method to apply the query to the database and obtain the result as a Rows object, with one item for each table row that matched your query.
  • For each non-unique index defined for the table, there is a corresponding GetFromIdx method to make retrieving data via the indexes easy.
Unique indexes are handled through the RelationDefinitionHeadingLinkRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a GetFromReader(SoDataReader, RelationDefinitionHeadingLinkTableInfo) method to retrieve the results of queries that return more than one row (this method will iterate over the reader to fetch ALL results, so beware of fetching huge result sets).

FindAll(Predicate<RelationDefinitionHeadingLinkRow>)

Return a new collection that contains only those elements that match the condition. Elements are shared, not clones! of the original collection

Declaration
public RelationDefinitionHeadingLinkRows FindAll(Predicate<RelationDefinitionHeadingLinkRow> condition)
Parameters
Type Name Description
Predicate<RelationDefinitionHeadingLinkRow> condition
Returns
Type Description
RelationDefinitionHeadingLinkRows
Remarks

Row collections can be created in several ways.

  • Use the static CreateNew() method to create a new, empty collection. You can then add objects of type RelationDefinitionHeadingLinkRow to it, and use methods like to operate on the whole collection.
  • You can create a (nested) RelationDefinitionHeadingLinkRows RelationDefinitionHeadingLinkRows.CustomSearch object to obtain a query pre-populated with the correct tableinfo and return fields. This query can be modified with restrictions, etc. Then, use the static GetFromCustomSearch(RelationDefinitionHeadingLinkRows.CustomSearch) method to apply the query to the database and obtain the result as a Rows object, with one item for each table row that matched your query.
  • For each non-unique index defined for the table, there is a corresponding GetFromIdx method to make retrieving data via the indexes easy.
Unique indexes are handled through the RelationDefinitionHeadingLinkRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a GetFromReader(SoDataReader, RelationDefinitionHeadingLinkTableInfo) method to retrieve the results of queries that return more than one row (this method will iterate over the reader to fetch ALL results, so beware of fetching huge result sets).

ForEach(Action<RelationDefinitionHeadingLinkRow>)

Method that iterates over all members and applies the action parameter to each of them

Declaration
public void ForEach(Action<RelationDefinitionHeadingLinkRow> whatToDo)
Parameters
Type Name Description
Action<RelationDefinitionHeadingLinkRow> whatToDo
Remarks

Row collections can be created in several ways.

  • Use the static CreateNew() method to create a new, empty collection. You can then add objects of type RelationDefinitionHeadingLinkRow to it, and use methods like to operate on the whole collection.
  • You can create a (nested) RelationDefinitionHeadingLinkRows RelationDefinitionHeadingLinkRows.CustomSearch object to obtain a query pre-populated with the correct tableinfo and return fields. This query can be modified with restrictions, etc. Then, use the static GetFromCustomSearch(RelationDefinitionHeadingLinkRows.CustomSearch) method to apply the query to the database and obtain the result as a Rows object, with one item for each table row that matched your query.
  • For each non-unique index defined for the table, there is a corresponding GetFromIdx method to make retrieving data via the indexes easy.
Unique indexes are handled through the RelationDefinitionHeadingLinkRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a GetFromReader(SoDataReader, RelationDefinitionHeadingLinkTableInfo) method to retrieve the results of queries that return more than one row (this method will iterate over the reader to fetch ALL results, so beware of fetching huge result sets).

GetFromCustomSearch(RelationDefinitionHeadingLinkRows.CustomSearch)

Create a new instance of the RelationDefinitionHeadingLinkRows object, and populate it with data from a custom search. If the search returns no results, an empty collection will be returned; if the result contains rows, a collection of RelationDefinitionHeadingLinkRow objects representing each row will be returned.

Declaration
public static RelationDefinitionHeadingLinkRows GetFromCustomSearch(RelationDefinitionHeadingLinkRows.CustomSearch query)
Parameters
Type Name Description
RelationDefinitionHeadingLinkRows.CustomSearch query

The custom search to execute against the database
Returns
Type Description
RelationDefinitionHeadingLinkRows

A new instance of the RelationDefinitionHeadingLinkRows object, reflecting the result of the query.
Remarks

Row collections can be created in several ways.

  • Use the static CreateNew() method to create a new, empty collection. You can then add objects of type RelationDefinitionHeadingLinkRow to it, and use methods like to operate on the whole collection.
  • You can create a (nested) RelationDefinitionHeadingLinkRows RelationDefinitionHeadingLinkRows.CustomSearch object to obtain a query pre-populated with the correct tableinfo and return fields. This query can be modified with restrictions, etc. Then, use the static GetFromCustomSearch(RelationDefinitionHeadingLinkRows.CustomSearch) method to apply the query to the database and obtain the result as a Rows object, with one item for each table row that matched your query.
  • For each non-unique index defined for the table, there is a corresponding GetFromIdx method to make retrieving data via the indexes easy.
Unique indexes are handled through the RelationDefinitionHeadingLinkRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a GetFromReader(SoDataReader, RelationDefinitionHeadingLinkTableInfo) method to retrieve the results of queries that return more than one row (this method will iterate over the reader to fetch ALL results, so beware of fetching huge result sets).

GetFromIdxHeadingId(Int32)

Create a new instance of the RelationDefinitionHeadingLinkRow object, by querying the database table via the index 'IDXRelDefHLHeading_id'. This method is intended to make it easy to use efficient queries that match a database index.

Declaration
public static RelationDefinitionHeadingLinkRows GetFromIdxHeadingId(int headingId)
Parameters
Type Name Description
Int32 headingId
Returns
Type Description
RelationDefinitionHeadingLinkRows

Row object that represents the result of the search. will be true if the query did not match any row in the table
Remarks

This method represents one of the unique indexes on the RelationDefinitionHeadingLink table. Non-unique indexes have corresponding inner classes and methods in the RelationDefinitionHeadingLinkRows collection, since they may return more than one row.

GetFromIdxReldefId(Int32)

Create a new instance of the RelationDefinitionHeadingLinkRow object, by querying the database table via the index 'IDXRelDefHLReldef_id'. This method is intended to make it easy to use efficient queries that match a database index.

Declaration
public static RelationDefinitionHeadingLinkRows GetFromIdxReldefId(int reldefId)
Parameters
Type Name Description
Int32 reldefId
Returns
Type Description
RelationDefinitionHeadingLinkRows

Row object that represents the result of the search. will be true if the query did not match any row in the table
Remarks

This method represents one of the unique indexes on the RelationDefinitionHeadingLink table. Non-unique indexes have corresponding inner classes and methods in the RelationDefinitionHeadingLinkRows collection, since they may return more than one row.

GetFromReader(SoDataReader, RelationDefinitionHeadingLinkTableInfo)

Create a new instance of the RelationDefinitionHeadingLinkRows object, and populate it with data from a reader. If the search returns no results, an empty collection will be returned; if the result contains rows, a collection of RelationDefinitionHeadingLinkRow objects representing each row will be returned.

Note that the internal logic starts by calling reader.Read(), which is correct if you hand the method the result of an ExecuteReader(), but if the reader has already been advanced one or more rows, the current row will be skipped and collection population will start with the next row.
Declaration
public static RelationDefinitionHeadingLinkRows GetFromReader(SoDataReader reader, RelationDefinitionHeadingLinkTableInfo tableInfo)
Parameters
Type Name Description
SoDataReader reader

SoDataReader positioned to a valid database row.
RelationDefinitionHeadingLinkTableInfo tableInfo

RelationDefinitionHeadingLinkTableInfo instance used in the query that is the source of the reader. The fields used from the reader will be those owned by this tableinfo object.
Returns
Type Description
RelationDefinitionHeadingLinkRows
Remarks

Row collections can be created in several ways.

  • Use the static CreateNew() method to create a new, empty collection. You can then add objects of type RelationDefinitionHeadingLinkRow to it, and use methods like to operate on the whole collection.
  • You can create a (nested) RelationDefinitionHeadingLinkRows RelationDefinitionHeadingLinkRows.CustomSearch object to obtain a query pre-populated with the correct tableinfo and return fields. This query can be modified with restrictions, etc. Then, use the static GetFromCustomSearch(RelationDefinitionHeadingLinkRows.CustomSearch) method to apply the query to the database and obtain the result as a Rows object, with one item for each table row that matched your query.
  • For each non-unique index defined for the table, there is a corresponding GetFromIdx method to make retrieving data via the indexes easy.
Unique indexes are handled through the RelationDefinitionHeadingLinkRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a GetFromReader(SoDataReader, RelationDefinitionHeadingLinkTableInfo) method to retrieve the results of queries that return more than one row (this method will iterate over the reader to fetch ALL results, so beware of fetching huge result sets).

Remove(RelationDefinitionHeadingLinkRow)

Removes the given RelationDefinitionHeadingLinkRow from the collection

Declaration
public void Remove(RelationDefinitionHeadingLinkRow row)
Parameters
Type Name Description
RelationDefinitionHeadingLinkRow row

the RelationDefinitionHeadingLinkRow to be removed
Remarks

Row collections can be created in several ways.

  • Use the static CreateNew() method to create a new, empty collection. You can then add objects of type RelationDefinitionHeadingLinkRow to it, and use methods like to operate on the whole collection.
  • You can create a (nested) RelationDefinitionHeadingLinkRows RelationDefinitionHeadingLinkRows.CustomSearch object to obtain a query pre-populated with the correct tableinfo and return fields. This query can be modified with restrictions, etc. Then, use the static GetFromCustomSearch(RelationDefinitionHeadingLinkRows.CustomSearch) method to apply the query to the database and obtain the result as a Rows object, with one item for each table row that matched your query.
  • For each non-unique index defined for the table, there is a corresponding GetFromIdx method to make retrieving data via the indexes easy.
Unique indexes are handled through the RelationDefinitionHeadingLinkRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a GetFromReader(SoDataReader, RelationDefinitionHeadingLinkTableInfo) method to retrieve the results of queries that return more than one row (this method will iterate over the reader to fetch ALL results, so beware of fetching huge result sets).

ToArray()

Heading link table for RelDef, for MDO headers Collection of RelationDefinitionHeadingLinkRow. Each element of the collection represents one row in the RelationDefinitionHeadingLink table.

Declaration
public RelationDefinitionHeadingLinkRow[] ToArray()
Returns
Type Description
RelationDefinitionHeadingLinkRow[]
Remarks

Row collections can be created in several ways.

  • Use the static CreateNew() method to create a new, empty collection. You can then add objects of type RelationDefinitionHeadingLinkRow to it, and use methods like to operate on the whole collection.
  • You can create a (nested) RelationDefinitionHeadingLinkRows RelationDefinitionHeadingLinkRows.CustomSearch object to obtain a query pre-populated with the correct tableinfo and return fields. This query can be modified with restrictions, etc. Then, use the static GetFromCustomSearch(RelationDefinitionHeadingLinkRows.CustomSearch) method to apply the query to the database and obtain the result as a Rows object, with one item for each table row that matched your query.
  • For each non-unique index defined for the table, there is a corresponding GetFromIdx method to make retrieving data via the indexes easy.
Unique indexes are handled through the RelationDefinitionHeadingLinkRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a GetFromReader(SoDataReader, RelationDefinitionHeadingLinkTableInfo) method to retrieve the results of queries that return more than one row (this method will iterate over the reader to fetch ALL results, so beware of fetching huge result sets).

ToString()

For debugging: Number of members, and the first (up to) 5 items

Declaration
public override string ToString()
Returns
Type Description
String
Remarks

Row collections can be created in several ways.

  • Use the static CreateNew() method to create a new, empty collection. You can then add objects of type RelationDefinitionHeadingLinkRow to it, and use methods like to operate on the whole collection.
  • You can create a (nested) RelationDefinitionHeadingLinkRows RelationDefinitionHeadingLinkRows.CustomSearch object to obtain a query pre-populated with the correct tableinfo and return fields. This query can be modified with restrictions, etc. Then, use the static GetFromCustomSearch(RelationDefinitionHeadingLinkRows.CustomSearch) method to apply the query to the database and obtain the result as a Rows object, with one item for each table row that matched your query.
  • For each non-unique index defined for the table, there is a corresponding GetFromIdx method to make retrieving data via the indexes easy.
Unique indexes are handled through the RelationDefinitionHeadingLinkRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a GetFromReader(SoDataReader, RelationDefinitionHeadingLinkTableInfo) method to retrieve the results of queries that return more than one row (this method will iterate over the reader to fetch ALL results, so beware of fetching huge result sets).

Implements

Extension Methods

EnumUtil.MapEnums<From, To>(From)