Version 2.0 has an action language that solves this problem and related
problems. You associate actions with particular element types.
For example, the problem described in the scenario is that an invoice
contains information about a part, but the part information might
already be in the database. In this case, you would use the
UpdateOrInsert action or the SoftInsert action for the Part element
The UpdateOrInsert action tells XML-DBMS to update the part information
if it already exists and insert it if it doesn't. The SoftInsert action
tells XML-DBMS to ignore the part information if it already exists and
insert it if it doesn't.
Other actions are:
None: Do nothing. The element exists to provide
context, such as key values.
Insert: Insert the row; throw an error if it exists.
Update: Update the row; throw an error if it does not
Delete: Delete the row; throw an error if it does not
SoftDelete: Same as Delete, except no error is thrown.
(It would probably be useful to have an action that checked that the
data exists and throw an error if it doesn't. For example, you might
only want to accept invoices for parts that are already in your
> Hi Ron!
> There are some mails in the archive about "insert_new"-option and others for a
> problem I have with 1:n assosiations in my xml file. (See scenario 3 in
> Is this already implemented in 1.01 or 2.0alpha3 (Java)?