DataReader vs DataSet

DataReader
       I.            DatReader works on a Connection oriented architecture.
    II.            DataReader is read only, forward only. It reads one record at atime. After DataReader finishes reading the current record, it moves to the next record. There is no way you can go back to the previous record. So using a DataReader you read in forward direction only.
 III.            Updations are not possible with DataReader.
IV.            As DataReader is read only, forward only it is much faster than a DataSet.

DataSet
       I.            DataSet works on disconnected architecture.
    II.            Using a DataSet you can move in both directions. DataSet is bi directional.
 III.            Database can be updated from a DataSet.
IV.            DataSet is slower than DataReader.

Related Posts:

  • SQL - Date and Time Functions Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4 … Read More
  • SQL Objective Type Question & Answers For Interview Q.1An entity set that does not have sufficient attributes to form a primary key is a (A) strong entity set. (B) weak entity set. (C) simple entity set. (D) primary entity set. Ans: B Q.2 Errors occur more often when a. data… Read More
  • DataReader vs DataSet DataReader        I.            DatReader works on a Connection oriented architecture.     II.    &nb… Read More
  • Bubble Sort Bubble sort [string array] #include <stdio.h> #include <stdlib.h> #include <string.h> #define MAX 50 #define N 2000 void sort_words(char *x[], int y); void swap(char **, char **); int main(void) {  … Read More
  • SQL Objective Type Question and Answers Database Objective Type  Question and Answers Q.1 In the relational modes, cardinality is termed as: (A) Number of tuples. (B) Number of attributes. (C) Number of tables. (D) Number of constraints. Ans: A Q.2… Read More

0 comments:

Post a Comment