Hi ,
it seems that new MODDB Actions doesn't alway's process the tables in the
right order.
In my understanding the processorder of the tables is determined by their
order in the table-set element.
Under some circumstances this order is violated.
here a small example (snippet from database.xml):
<!-- working example -->
<table name="dataobject" alias="dataobject">
...
</table>
<table name="address" alias="address">
...
</table>
<table-set name="Address">
<table name="dataobject"/>
<table name="address"/>
</table-set>
this works for me.
<!-- no working example -->
<table name="address" alias="address">
...
</table>
<table name="dataobject" alias="dataobject">
...
</table>
<table-set name="Address">
<table name="dataobject"/>
<table name="address"/>
</table-set>
Only the order of tabledefinition is changed in these examples.
On Processing the "table-set" named "Address" first the table "address" is
processed afterthat the action works on table "dataobject".
I figured out that the table-definition order is important.
Is this the proper way to work or a bug ?
frank
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
