Datasets in framework 2.0
- From: eugenet@xxxxxxxxxx
- Date: 11 Sep 2006 09:09:09 -0700
Hello,
In ASP.NET 1.1, I followed this data access methodology:
At design time
- Create a strongly typed dataset
- Add this dataset to a form and bind controls to the dataset using
the designer
At run time
- Fill dataset with data on the first load of the page
- Handle all Add/Edit/Delete operations against the in-memory copy
of my dataset
- Persist the dataset between postbacks in session
- Give users the ability to Save or Cancel changes, which either
persists the changes to the database or discards them.
It worked like a charm -- there were only two trips to the database --
in the very beginning and at the very end. In memory manipulations were
very fast. And, more importantly, my productivity was high because I
was able to use design features of the Visual Studio.
It seems that in 2005, if I were to pursue the same methodology, things
would be harder, not easier.
- It appears that the only way to bind a dataset to a gridview is
through the ObjectDataSource. This binds to data adapters, not the
actual dataset, so, the database gets hit on each update.
- DataSource property is gone from the design view, so I no longer can
use the design features of Visual Studio, if I were to directly bind to
a dataset.
- There is no out of the box feature to persist a dataset between
postbacks. So, like in 1.1, if I were to go this route, I would have to
persist it in session.
I was wondering if there is anybody out there who used the 1.1 data
access in a similar fashion, and how you adapted to 2.0.
Thank you for your comments.
Evgueni
.
- Follow-Ups:
- Re: Datasets in framework 2.0
- From: Eliyahu Goldin
- Re: Datasets in framework 2.0
- Prev by Date: Re: Passing array of numbers to SQL query
- Next by Date: Re: Best tool for JavaScript debugging
- Previous by thread: The remote server returned an error: (405) Method Not Allowed.
- Next by thread: Re: Datasets in framework 2.0
- Index(es):
Relevant Pages
|
