MACROMEDIA FLASH MX 2004-USING FLASH Use Manual page 306

The following table describes how the key attributes value is determined. If a field is defined as a
key field, using the RDBMSResolver component's
the update packet with
be set according to the following table:
Node type
delete
insert
update
About receiving results from an external data source
This section describes requirements that your server code must fulfill. After the server finishes
with the update packet, either successfully or unsuccessfully, it should send back a result packet
containing errors or additional updates resulting from the update operation. If there are no
messages, the results packet should still be sent, but it will have no operation result nodes.
The following example shows a sample RDBMSResolver component results packet (with both
update results and change information nodes):
<results_packet nullValue="{_NULL_}" transID="46386292065:Wed Jun 25 15:52:34
GMT-0700 2003">
<operation op="delete" id="11295627479" msg="The record could not be
found"/>
<delete>
<field name="id" oldValue="1000" key="true" />
</delete>
<insert>
<field name="id" newValue="20"/>
<field name="firstName" newValue="Davey"/>
<field name="lastName" newValue="Jones"/>
</insert>
<operation op="update" id="02938027477" msg="Couldn't update employee.">
<field name="id" curValue="105" msg="Invalid field value" />
</operation>
<update>
<field name="id" oldValue="30" newValue="30" key="true" />
<field name="firstName" oldValue="Peter" newValue="Mickey"/>
<field name="lastName" oldValue="Tork" newValue="Dolenz"/>
</update>
</results_packet>
The results packet contains four types of nodes:
Operation
nodes contain the result of operations from the update packet. Each operation node
should have the following attributes/child nodes:
•
The attribute describes the type of operation that was attempted. Must be insert, delete,
op
or update.
•
The attribute holds the ID from the operation node that was sent out
id
306 Chapter 14: Data Integration (Flash Professional Only)
. Otherwise, the field's key attribute in the update packet will
key="true"
umUsingKey
false
false
false
parameter, it will always appear in
fieldInfo
umUsingModified
true
true
if the field was
true
modified; otherwise
false
umUsingAll
true
false
true