Hi,
does it make sense to hide values for which the input-module gives null as
result ?
maybe the descriptor file can contain a nullable attribute for the these
column's (of course only for values not for keys):
<table name="emailaddress" alias="emailaddress" label="Email">
<keys>
...
</keys>
<values>
<value name="kindofuse" type="string"></value>
<value name="locator" type="string"></value>
<value name="notes" type="string" nullable="true"></value> <! --
optional field -->
</values>
</table>
why this ?
the current behaviour forces you to feed each value, for each row being
updated, into the request as a hidden parameter. If i leave the fields
blank or more likely they don't exist- the update statement overrides
existing values with null.
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
