ASP.NET TableAdapter Update - How does it work?

Question

0.00/5 (No votes)

See more:

I am building a website as a school project, which uses ASP.NET webservice. I am implementing the DAL, BLL structure in my webservice. As mentioned in most of the articles, the tableAdapter automatically generates the update method (the option is selected). In the BLL, I have a function called UpdateInformation , which in turn calls the tableAdapter.Update(). I want to know how does the TableAdapter.Update() method actually execute? To be more precise, if the user has updated only say 1 of the fields, does the update method still update all of the fields in the database? Or is it smart enough to only update the fields that have been changed?
If it is updating all fields no matter what, then my professor has suggested making individual updates for each field. Is that feasible?

I am trying to make the design as good as possible, as someone else will be continuing with this project once I graduate.

Posted 23-Jun-10 13:54pm

Batul Saifee

Updated 23-Jun-10 13:55pm

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

kornakar · Accepted Answer · 2010-06-23T20:17:00

"I am trying to make the design as good as possible".

Making update methods for every field is not a good design. Your professor is cleary making premature optimizations based on intuition and old systems with inadequate CPU power.

By using only one update method the design stays simple and intuitive in all situations (the programmer doesn't have to worry about thinking what field has changed and when, just set the values and call Update). Also, think about the situation when you have changed, say, five fields. That makes five UPDATE's and is quite a stress on the database server (compared to only one, a bit larger UPDATE).

Even the NHibernate updates all field regardless of what has changed (this can be changed, though, but it makes it slower).