DbDataAdapter::Fill Method (DataSet^)
Adds or refreshes rows in the DataSet.
Assembly: System.Data (in System.Data.dll)
Return ValueType: System::Int32
The number of rows successfully added to or refreshed in the DataSet. This does not include rows affected by statements that do not return rows.
The IDbConnection object associated with the select command must be valid, but it does not need to be open. If the IDbConnection is closed before is called, it is opened to retrieve data and then closed. If the connection is open before is called, it remains open.method retrieves the data from the data source using a SELECT statement. The
If an error or an exception is encountered while populating the data tables, rows added prior to the occurrence of the error remain in the data tables. The remainder of the operation is aborted.
If a command does not return any rows, no tables are added to the DataSet, and no exception is raised.
If the DbDataAdapter object encounters duplicate columns while populating a DataTable, it generates names for the subsequent columns using the pattern "columnname1", "columnname2", "columnname3", and so on. If the incoming data contains unnamed columns, they are placed in the DataSet according to the pattern "Column1", "Column2", and so on.
When the query specified returns multiple results, the result set for each row returning query is placed in a separate table. Additional result sets are named by appending integral values to the specified table name (for example, "Table", "Table1", "Table2", and so on). Because no table is created for a query that does not return rows, if you process an insert query followed by a select query, the table created for the select query is named "Table" because it is the first table created. Applications using column and table names should ensure that conflicts with these naming patterns does not occur.
When the SELECT statement used to populate the DataSet returns multiple results, such as batch SQL statements, if one of the results contains an error, all subsequent results are skipped and are not added to the DataSet.
When using subsequent DataSet, two conditions must be met:calls to refresh the contents of the
The SQL statement should match the one initially used to populate the DataSet.
The Key column information must be present.
If primary key information is present, any duplicate rows are reconciled and only appear once in the DataTable that corresponds to the DataSet. Primary key information may be set either through FillSchema, by specifying the PrimaryKey property of the DataTable, or by setting the MissingSchemaAction property to AddWithKey.
If the SelectCommand returns the results of an OUTER JOIN, the DataAdapter does not set a PrimaryKey value for the resulting DataTable. You must explicitly define the primary key to ensure that duplicate rows are resolved correctly. For more information, see Defining Primary Keys.
When handling batch SQL statements that return multiple results, the implementation of FillSchema for the .NET Framework Data Provider for OLE DB retrieves schema information for only the first result. To retrieve schema information for multiple results, use with the MissingSchemaAction set to AddWithKey.
Available since 1.1