DataAdapter with different SQL's
- From: ivanfernandes@xxxxxxxxxxxxx
- Date: 30 Aug 2005 08:12:54 -0700
Hello,
Created dataadapter select with this command
"select * from emp where empid IN (123,456,789)";
Filled and sent dataset to remote client. lost original dataadapter
Remote client works with the dataset and sends it back
Created a new dataadapter select with this command
"select * from emp where 1=2; (effectively a null set)
populate the update/insert/deletes commands on the dataadapter based on
the 2nd above select
Called the Update method of the dataadapter.
All changes get affected to the database.
Question 1 : Can/should i create the dataset with one select command
and at time of update create another select command based on a
different sql. (i use this method as when i pass the dataset to the
remote site i dont pass the parameters used to create the original sql,
so at time of return i dont know/unaware of the original sql).
Question 2 : Does this mean that dataadapter works in such a way that
it needs only to know the end table & fields without knowing the
original data associated, i.e. the dataset set has all the intellegence
of old rows/newsrows contained in it.
Thanks
Ivan
.
- Follow-Ups:
- Re: DataAdapter with different SQL's
- From: AMDRIT
- Re: DataAdapter with different SQL's
- Prev by Date: RE: SQL debugging
- Next by Date: Re: Auto update data on RowChanged
- Previous by thread: Rowfilter on child recorsd only works with Fill
- Next by thread: Re: DataAdapter with different SQL's
- Index(es):
Relevant Pages
|
Loading