forked from dotnet/docs
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathns-System.Data.xml
21 lines (15 loc) · 2.82 KB
/
ns-System.Data.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
<Namespace Name="System.Data">
<Docs>
<summary>The <see cref="N:System.Data" /> namespace provides access to classes that represent the ADO.NET architecture. ADO.NET lets you build components that efficiently manage data from multiple data sources.</summary>
<remarks>
<format type="text/markdown"><![CDATA[
## Remarks
In a disconnected scenario such as the Internet, ADO.NET provides the tools to request, update, and reconcile data in multiple tier systems. The ADO.NET architecture is also implemented in client applications, such as Windows Forms, or HTML pages created by ASP.NET.
The centerpiece of the ADO.NET architecture is the <xref:System.Data.DataSet> class. Each <xref:System.Data.DataSet> can contain multiple <xref:System.Data.DataTable> objects, with each <xref:System.Data.DataTable> containing data from a single data source, such as SQL Server.
Each <xref:System.Data.DataTable> contains a <xref:System.Data.DataColumnCollection>--a collection of <xref:System.Data.DataColumn> objects--that determines the schema of each <xref:System.Data.DataTable>. The <xref:System.Data.DataColumn.DataType%2A> property determines the type of data held by the <xref:System.Data.DataColumn>. The <xref:System.Data.DataColumn.ReadOnly%2A> and <xref:System.Data.DataColumn.AllowDBNull%2A> properties let you further guarantee data integrity. The <xref:System.Data.DataColumn.Expression%2A> property lets you construct calculated columns.
If a <xref:System.Data.DataTable> participates in a parent/child relationship with another <xref:System.Data.DataTable>, the relationship is constructed by adding a <xref:System.Data.DataRelation> to the <xref:System.Data.DataRelationCollection> of a <xref:System.Data.DataSet> object. When such a relation is added, a <xref:System.Data.UniqueConstraint> and a <xref:System.Data.ForeignKeyConstraint> are both created automatically, depending on the parameter settings for the constructor. The <xref:System.Data.UniqueConstraint> guarantees that values that are contained in a column are unique. The <xref:System.Data.ForeignKeyConstraint> determines what action will happen to the child row or column when a primary key value is changed or deleted.
Using the <xref:System.Data.SqlClient> namespace (the.NET Framework Data Provider for SQL Server), the <xref:System.Data.Odbc> namespace (the.NET Framework Data Provider for ODBC), the <xref:System.Data.OleDb> namespace (the.NET Framework Data Provider for OLE DB), or the <xref:System.Data.OracleClient> namespace (the .NET Framework Data Provider for Oracle), you can access a data source to use together with a <xref:System.Data.DataSet>. Each.NET Framework data provider has a corresponding **DataAdapter** that you use as a bridge between a data source and a <xref:System.Data.DataSet>.
]]></format>
</remarks>
</Docs>
</Namespace>