The applications use APIs to process or get details from
the database by passing queries as strings, or calling database objects by passing
parameters. So what is the purpose of LINQ here? Presently scenario, we see a lot of
applications, especially multi-tier applications, having a separate data access layer
and a business logic layer. If we take the business logic layer, we must have lots of
entities or objects to hold the information. These objects represent the database table
rows in the form of objects. We use object references similar to primary keys in the
database to identify a set of information.
To get data from a relational database to an application, the programmer ends
up creating two different types of objects, but in different formats. The other
disadvantage is that the programmer has to pass relational database queries as text
strings from the application, then get it executed from the relational database, and
pass on the information to the application objects or entity objects.
Pages:
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26