Morphing UPDATEs

  • Thread starter Thread starter William \(Bill\) Vaughn
  • Start date Start date
W

William \(Bill\) Vaughn

I was wrong. When the CommandBuilder is hooked to the DataAdapter, the
UPDATE statements generated DO morph from row-to-row. This way only the
changed columns are SET. This is a good feature, but given the other
limitations of the CB, I still can't recommend its use.

When you use hand-written UPDATE commands (set the DataAdapter
UpdateCommand), the SQL is invariant. Except for input parameters, the SQL
does not change from row to row.

I apologize for any confusion.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
www.sqlreportingservices.net
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
 
They have a CommandBuilder in the DataAdapter? :-)

Bill, I have long been under the impression that the CommandBuilder is only
useful for very simple applications or prototypes. Beyond that, it becomes
more of a hindrance than a help.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************
 
George
Bill, I have long been under the impression that the CommandBuilder is
only
useful for very simple applications or prototypes. Beyond that, it becomes
more of a hindrance than a help.
Click to expand...
Why in my opinion is in a project is the majority of the updates simple.

(Going to the limits of 100 columns per table, what is impossible for the
commandbuilder, is in my opinion only a problem at fools design)

Just my opinion.

Cor
 
Back
Top