April 2003
Beginner to intermediate
620 pages
21h 48m
English
Content preview from ADO.NET in a NutshellBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Chapter 34. The System.Data Namespace
The
System.Data namespace represents the core of
ADO.NET. It contains the fundamental data container classes such as
DataSet. Every DataSet
contains a collection of DataTable instances. Each
DataTable holds a collection of
DataRow objects, each of which contains the data
for a single row. These data classes are independent of any ADO.NET
provider. They simply store disconnected data. In addition, the
DataSet also contains objects that describe
structural information about your data. This structural information,
which is also known as metadata, includes
column-specific settings such as data type (found in
DataColumn), foreign key and unique column
constraints (represented by ForeignKeyConstraint
and UniqueConstraint), and relations that link
columns in different tables (represented by
DataRelation).
Taken together, these objects act like an in-memory relational
database, complete with versioning, column and table information, XML
output, and automatic enforcement of identity and relational
integrity rules. However, these classes are only part of the
System.Data namespace. You’ll
also find the interfaces that must be implemented by every ADO.NET
provider. These interfaces define connections
(IDbConnection), commands
(IDbCommand), data readers
(IDataReader), parameters
(IDbDataParameter), transactions
(IDbTransaction), and data adapters
(IDbDataAdapter and
IDataAdapter). These interfaces aren’t just a low-level part of ADO.NET. You’ll need to ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.