Class EmailAccountRows

Email account information Collection of EmailAccountRow. Each element of the collection represents one row in the EmailAccount table.

Inheritance
object
NestedPersist
NestedPersistFacade
NestedCollectionPersist
TableRowsBase
EmailAccountRows
Inherited Members
Namespace: SuperOffice.CRM.Rows
Assembly: SoDataBase.dll
Syntax
public class EmailAccountRows : TableRowsBase, INestedPersist, IEnumerable<INestedPersist>, INotifyCollectionChanged, IBindingList, IList, ICollection, IEnumerable
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 EmailAccountRow to it, and use methods like Save to operate on the whole collection.
  • You can create a (nested) EmailAccountRows EmailAccountRows.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 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 EmailAccountRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a SuperOffice.CRM.Rows.EmailAccountRows.GetFromReader 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

this[int]

Get a EmailAccountRow given its index in the collection.

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

Index of the EmailAccountRow in the collection
Property Value
Type Description
EmailAccountRow
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 EmailAccountRow to it, and use methods like Save to operate on the whole collection.
  • You can create a (nested) EmailAccountRows EmailAccountRows.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 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 EmailAccountRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a SuperOffice.CRM.Rows.EmailAccountRows.GetFromReader 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(EmailAccountRow)

Add one EmailAccountRow to the collection.

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

An instance of EmailAccountRow to be added to the collection.
Returns
Type Description
int

The index of the added EmailAccountRow.
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 EmailAccountRow to it, and use methods like Save to operate on the whole collection.
  • You can create a (nested) EmailAccountRows EmailAccountRows.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 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 EmailAccountRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a SuperOffice.CRM.Rows.EmailAccountRows.GetFromReader 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 EmailAccountRow added to the collection.

Declaration
public EmailAccountRow AddNew()
Returns
Type Description
EmailAccountRow

A new instance of EmailAccountRow 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 EmailAccountRow to it, and use methods like Save to operate on the whole collection.
  • You can create a (nested) EmailAccountRows EmailAccountRows.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 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 EmailAccountRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a SuperOffice.CRM.Rows.EmailAccountRows.GetFromReader 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<EmailAccountRow>)

Add a range of EmailAccountRow to the collection.

Declaration
public EmailAccountRows AddRange(IEnumerable<EmailAccountRow> rows)
Parameters
Type Name Description
IEnumerable<EmailAccountRow> rows
Returns
Type Description
EmailAccountRows

The updated EmailAccountRows 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 EmailAccountRow to it, and use methods like Save to operate on the whole collection.
  • You can create a (nested) EmailAccountRows EmailAccountRows.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 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 EmailAccountRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a SuperOffice.CRM.Rows.EmailAccountRows.GetFromReader 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 EmailAccountRow

Declaration
protected override TableRowBase CreateChild()
Returns
Type Description
TableRowBase

New instance of EmailAccountRow
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 EmailAccountRow to it, and use methods like Save to operate on the whole collection.
  • You can create a (nested) EmailAccountRows EmailAccountRows.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 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 EmailAccountRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a SuperOffice.CRM.Rows.EmailAccountRows.GetFromReader 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 EmailAccountRows object. This collection will contain no rows.

Declaration
public static EmailAccountRows CreateNew()
Returns
Type Description
EmailAccountRows

A new instance of the EmailAccountRows 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 EmailAccountRow to it, and use methods like Save to operate on the whole collection.
  • You can create a (nested) EmailAccountRows EmailAccountRows.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 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 EmailAccountRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a SuperOffice.CRM.Rows.EmailAccountRows.GetFromReader 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<EmailAccountRow>)

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

Declaration
public EmailAccountRow Find(Predicate<EmailAccountRow> condition)
Parameters
Type Name Description
Predicate<EmailAccountRow> condition
Returns
Type Description
EmailAccountRow
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 EmailAccountRow to it, and use methods like Save to operate on the whole collection.
  • You can create a (nested) EmailAccountRows EmailAccountRows.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 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 EmailAccountRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a SuperOffice.CRM.Rows.EmailAccountRows.GetFromReader 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<EmailAccountRow>)

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

Declaration
public EmailAccountRows FindAll(Predicate<EmailAccountRow> condition)
Parameters
Type Name Description
Predicate<EmailAccountRow> condition
Returns
Type Description
EmailAccountRows
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 EmailAccountRow to it, and use methods like Save to operate on the whole collection.
  • You can create a (nested) EmailAccountRows EmailAccountRows.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 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 EmailAccountRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a SuperOffice.CRM.Rows.EmailAccountRows.GetFromReader 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<EmailAccountRow>)

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

Declaration
public void ForEach(Action<EmailAccountRow> whatToDo)
Parameters
Type Name Description
Action<EmailAccountRow> 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 EmailAccountRow to it, and use methods like Save to operate on the whole collection.
  • You can create a (nested) EmailAccountRows EmailAccountRows.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 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 EmailAccountRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a SuperOffice.CRM.Rows.EmailAccountRows.GetFromReader 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).

GetFromCustomSearchAsync(CustomSearch, CancellationToken)

Create a new instance of the EmailAccountRows 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 EmailAccountRow objects representing each row will be returned.

Declaration
public static Task<EmailAccountRows> GetFromCustomSearchAsync(EmailAccountRows.CustomSearch query, CancellationToken cancellationToken = default)
Parameters
Type Name Description
EmailAccountRows.CustomSearch query

The custom search to execute against the database
CancellationToken cancellationToken
Returns
Type Description
Task<EmailAccountRows>

A new instance of the EmailAccountRows 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 EmailAccountRow to it, and use methods like Save to operate on the whole collection.
  • You can create a (nested) EmailAccountRows EmailAccountRows.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 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 EmailAccountRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a SuperOffice.CRM.Rows.EmailAccountRows.GetFromReader 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).

GetFromIdxAssociateIdAsync(int, CancellationToken)

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

Declaration
public static Task<EmailAccountRows> GetFromIdxAssociateIdAsync(int associateId, CancellationToken cancellationToken = default)
Parameters
Type Name Description
int associateId
CancellationToken cancellationToken
Returns
Type Description
Task<EmailAccountRows>

Row object that represents the result of the search. IsNew 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 EmailAccount table. Non-unique indexes have corresponding inner classes and methods in the EmailAccountRows collection, since they may return more than one row.

GetFromReaderAsync(SoDataReader, EmailAccountTableInfo, CancellationToken)

Create a new instance of the EmailAccountRows 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 EmailAccountRow 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 Task<EmailAccountRows> GetFromReaderAsync(SoDataReader reader, EmailAccountTableInfo tableInfo, CancellationToken cancellationToken = default)
Parameters
Type Name Description
SoDataReader reader

SoDataReader positioned to a valid database row.
EmailAccountTableInfo tableInfo

EmailAccountTableInfo 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.
CancellationToken cancellationToken
Returns
Type Description
Task<EmailAccountRows>
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 EmailAccountRow to it, and use methods like Save to operate on the whole collection.
  • You can create a (nested) EmailAccountRows EmailAccountRows.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 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 EmailAccountRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a SuperOffice.CRM.Rows.EmailAccountRows.GetFromReader 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(EmailAccountRow)

Removes the given EmailAccountRow from the collection

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

the EmailAccountRow 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 EmailAccountRow to it, and use methods like Save to operate on the whole collection.
  • You can create a (nested) EmailAccountRows EmailAccountRows.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 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 EmailAccountRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a SuperOffice.CRM.Rows.EmailAccountRows.GetFromReader 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()

Email account information Collection of EmailAccountRow. Each element of the collection represents one row in the EmailAccount table.

Declaration
public EmailAccountRow[] ToArray()
Returns
Type Description
EmailAccountRow[]
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 EmailAccountRow to it, and use methods like Save to operate on the whole collection.
  • You can create a (nested) EmailAccountRows EmailAccountRows.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 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 EmailAccountRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a SuperOffice.CRM.Rows.EmailAccountRows.GetFromReader 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
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 EmailAccountRow to it, and use methods like Save to operate on the whole collection.
  • You can create a (nested) EmailAccountRows EmailAccountRows.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 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 EmailAccountRow object directly, which has nested classes and GetFromIdx methods for each unique index. Similarly, there is a SuperOffice.CRM.Rows.EmailAccountRows.GetFromReader 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