Some questions.

[Land]

Hi.
I have some questions about WebService.
Most time, we use a "identity" field as the primary key for the table in SQL
databse, and that "identity" primary key can be migrated to child table as
the foreign key. all those "identity" field will be filled by SQL system when
we insert record.
But for WebService, user input the information at client side, we don't know
the finial value of all those "identity" field before we insert all records
into SQL use WebServie. especially for child table. we need to fill the
foreign key depend on reture vale of parent's primary key. So how WebService
handle that condition?

[John Scragg]

SQL Server Side:

1) Use Stored Procs.
2) Get the SCOPE_IDENTITY() for your insert
3) Return that identity value either through an output parameter or as a
resultset.

Web Service Side:

If you are doing 1 update at a time through a WebMethod, you can have that
WebMethod return the identity value as its return value. Your client app
then updates its dataset/class/whatever with the value.

If you are inserting multiple records, you can have the WebMethod requery to
produce an updated copy of your dataset/class. You client app then gets a
new copy of the data to work with.

HTH,

John

"Land" wrote:

Hi.
I have some questions about WebService.
Most time, we use a "identity" field as the primary key for the table in SQL
databse, and that "identity" primary key can be migrated to child table as
the foreign key. all those "identity" field will be filled by SQL system when
we insert record.
But for WebService, user input the information at client side, we don't know
the finial value of all those "identity" field before we insert all records
into SQL use WebServie. especially for child table. we need to fill the
foreign key depend on reture vale of parent's primary key. So how WebService
handle that condition?